# phoenix Published articles for phoenix. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## First Clear Visuals Of Meta's Project Phoenix Headset Found In Quest Firmware DevFeed: [First Clear Visuals Of Meta's Project Phoenix Headset Found In Quest Firmware]() Original publisher: [Read original article]() Author: Luna Published: 2026-09-10T22:53:46Z Content type: news Language: en Sources: [UploadVR]() Topics: [Meta](), [phoenix](), [App](), [QR Code](), [Zip]() Tags: [devices](), [headsets-tech](), [meta](), [phoenix](), [qr-code](), [sensors](), [zip]() ### AI overview Meta's HorizonOS Prescription Lens app now contains clear visuals of the Project Phoenix headset. The images show prescription lens attachment and QR-code scanning, a slim glasses-style design with visible sensors, and a cable connecting the headset to a compute puck. ### Source excerpt The first visuals of Meta's Project Phoenix headset have been found in Horizon OS firmware, revealing a slim design with a tether for the compute puck. ## Selecting The Right AI Evals Tool DevFeed: [Selecting The Right AI Evals Tool]() Original publisher: [Read original article]() Author: Hamel Husain Published: 2025-10-01T07:00:00Z Content type: article Language: en Sources: [Hamel Husain]() Topics: [Artificial Intelligence](), [AI Engineering](), [Developer experience](), [LangChain](), [phoenix]() Tags: [ai](), [ai-engineering](), [ai-evals](), [analysis](), [developer-experience](), [evals](), [langchain](), [phoenix](), [quality]() ### AI overview The article examines how to select AI evaluation tools, arguing that no single tool is best for every team. It compares approaches from LangSmith, Braintrust, and Arize Phoenix through a shared assignment and highlights workflow, developer experience, SDK ergonomics, documentation, integrations, and human-in-the-loop support as selection criteria. ### Source excerpt Over the past year, I've focused heavily on AI Evals, both in my consulting work and teaching. A question I get constantly is, "What's the best tool for evals?". I've always resisted answering directly for two reasons. First, people focus too much on tools instead of the process, thinking the tool will be an off-the-shelf solution when it rarely is. Second, the tools change so quickly that comparisons become outdated immediately. Having used many of the popular eval tools, I can genuinely say that no single one is superior in every dimension. The "best" tool depends on your team's skillset, technical stack, and maturity. Instead of a feature-by-feature comparison, I think it's more valuable to show you how a panel of data scientists skilled in evals assesses these tools. As part of my AI Evals course, we had three of the most dominant vendors--Langsmith, Braintrust, and Arize Phoenix complete the same homework assignment. This gave us a unique opportunity to see how they tackle the exact same challenge. We recorded the entire process and live commentary, which is available below. We think this might be helpful in learning about the kinds of things you should consider when selecting a tool for your team. Thanks to Shreya Shankar and Bryan Bischof for serving as the panelists (alongside me). Langsmith With Harrison Chase, CEO of LangChain. Braintrust With Wayde Gilliam, former developer relations at Braintrust. Arize Phoenix With SallyAnn DeLucia, Technical AI Product Leader at Arize. Criteria for Assessing AI Evals Tools Here are themes that consistently surfaced during our review. 1. Workflow and Developer Experience Reducing friction is more important than any single feature. Concretely, you should be mindful of the time it takes to go from observing a failure to iterating on a solution. For example, we appreciated the ability to go from viewing a single trace to experimenting with that same trace in a playground. For some teams with data-science backgrounds, a note ## Phoenix.new - The Remote AI Runtime for Phoenix DevFeed: [Phoenix.new - The Remote AI Runtime for Phoenix]() Original publisher: [Read original article]() Published: 2025-06-20T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [phoenix](), [Elixir](), [Artificial Intelligence](), [Large Language Model](), [coding](), [fly.io](), [fly](), [browser](), [real-time](), [Visual Studio Code](), [Front end](), [JavaScript]() Tags: [agent](), [agents](), [ai](), [browser](), [cdn](), [close-to-users](), [coding](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [javascript](), [networking](), [phoenix](), [postgresql-clusters](), [real-time](), [servers](), [vscode]() ### AI overview Phoenix.new is a fully online coding agent tailored to Elixir and Phoenix. It runs in a browser-backed, isolated Fly Machine with shell access, a VSCode interface, and browser tools that let the agent inspect front-end changes and JavaScript state while building real-time collaborative applications. ### Source excerpt I'm Chris McCord, the creator of Elixir's Phoenix framework. For the past several months, I've been working on a skunkworks project at Fly.io, and it's time to show it off. I wanted LLM agents to work just as well with Elixir as they do with Python and JavaScript. Last December, in order to figure out what that was going to take, I started a little weekend project to find out how difficult it would be to build a coding agent in Elixir. A few weeks later, I had it spitting out working Phoenix applications and driving a full in-browser IDE. I knew this wasn't going to stay a weekend project. If you follow me on Twitter, you've probably seen me teasing this work as it picked up steam. We're at a point where we're pretty serious about this thing, and so it's time to make a formal introduction. World, meet Phoenix.new, a batteries-included fully-online coding agent tailored to Elixir and Phoenix. I think it's going to be the fastest way to build collaborative, real-time applications. Let's see it in action: What's Interesting About Phoenix.new First, even though it runs entirely in your browser, Phoenix.new gives both you and your agent a root shell, in an ephemeral virtual machine (a Fly Machine) that gives our agent loop free rein to install things and run programs -- without any risk of messing up your local machine. You don't think about any of this; you just open up the VSCode interface, push the shell button, and there you are, on the isolated machine you share with the Phoenix.new agent. Second, it's an agent system I built specifically for Phoenix. Phoenix is about real-time collaborative applications, and Phoenix.new knows what that means. To that end, Phoenix.new includes, in both its UI and its agent tools, a full browser. The Phoenix.new agent uses that browser "headlessly" to check its own front-end changes and interact with the app. Because it's a full browser, instead of trying to iterate on screenshots, the agent sees real page content and JavaScript state ## Trino's Upgrade to Java 24 DevFeed: [Trino's Upgrade to Java 24]() Original publisher: [Read original article]() Author: Manfred Moser, Mateusz Gajewski Published: 2025-03-03T00:00:00Z Content type: opinion Language: en Sources: [Trino Blog]() Topics: [Java](), [upgrade](), [Security](), [Kafka](), [phoenix]() Tags: [java](), [java-17](), [kafka](), [phoenix](), [release-notes](), [security](), [upgrade]() ### AI overview The article discusses Trino's upgrade from Java 23 to Java 24, highlighting selected Java 24 features and the expected impact of permanently disabling the Security Manager on Trino connectors and dependencies. ### Source excerpt Six month ago we adopted Java 23 as requirement, following our standard procedure to upgrade with each Java version as soon as it becomes available. This allows us to take advantage of all the great improvement each release brings. The upgrade to 23 was pretty easy since the changes from 22 to 23 were not that big. The story turns out to be a bit different now with our upgrade to Java 24. ## Trace & Evaluate your Agent with Arize Phoenix DevFeed: [Trace & Evaluate your Agent with Arize Phoenix]() Original publisher: [Read original article]() Author: Sri Chavali; John Gilhuly; Aymeric Roucher Published: 2025-02-28T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [phoenix](), [agent observability](), [smolagents](), [OpenTelemetry](), [tracing](), [telemetry](), [Human-AI evaluation]() Tags: [agent](), [agents](), [debug](), [evaluation](), [free](), [hosting](), [hugging-face](), [instrumentation](), [opentelemetry](), [performance](), [phoenix](), [smolagents](), [telemetry](), [tracing](), [visualization]() ### AI overview This tutorial explains how to trace, evaluate, and debug a smolagents agent with Arize Phoenix. It demonstrates an agent powered by the Hugging Face Hub Serverless API that searches for Google share-price data from 2020 to 2024 and creates a line graph, then instruments the workflow with OpenTelemetry and OpenInference. Phoenix can run locally, as a self-hosted application, or on Hugging Face Spaces. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## 30 Years of Decompilation and the Unsolved Structuring Problem: Part 2 DevFeed: [30 Years of Decompilation and the Unsolved Structuring Problem: Part 2]() Original publisher: [Read original article]() Published: 2024-01-10T00:00:00Z Content type: article Language: en Sources: [mahaloz.re]() Topics: [Programming](), [compilers](), [phoenix]() Tags: [compilers](), [deep-dive](), [ida](), [ida-pro](), [phoenix](), [research](), [security](), [technical]() ### AI overview Part 2 of a history of decompiler research examines modern control-flow structuring techniques, their limitations, and possible future directions. It reviews four papers from the past 11 years, including Phoenix, and places them in the context of security, compiler, static-analysis, and programming-language research. ### Source excerpt A two-part series on the history of decompiler research and the fight against the unsolved control flow structuring problem. In part 1, we revisit the history of foundational decompilers and techniques, concluding on a look at modern works. In part 2, we deep-dive into the fundamentals of modern control flow structuring techniques, and their limitations, and look to the future. ## Realtime: Multiplayer Edition DevFeed: [Realtime: Multiplayer Edition]() Original publisher: [Read original article]() Author: Wen Bo Xie; Stanislav Muzhyk Published: 2022-08-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [WebSocket](), [Elixir](), [phoenix](), [Databases](), [Replication](), [Open Source](), [JSON]() Tags: [database](), [elixir](), [features](), [general](), [json](), [open-source](), [phoenix](), [release](), [replication]() ### AI overview Supabase announces the general availability of Realtime multiplayer features, Broadcast and Presence. The features are available through the Realtime server and the new supabase-js release, with access for Supabase projects on the Free Plan and newer projects. The article also describes Realtime's Elixir and Phoenix-based architecture, which uses PostgreSQL logical replication, WebSockets, and JSON serialization to deliver database changes to clients. ### Source excerpt Announcing the general availability of Realtime's Broadcast and Presence. ## And Now For Starting Again with Elixir and Phoenix Not Elm DevFeed: [And Now For Starting Again with Elixir and Phoenix Not Elm]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-04-01T15:57:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Elixir](), [phoenix](), [Elm](), [Laravel](), [MySQL](), [Homebrew](), [Processes]() Tags: [code](), [elixir](), [elm](), [homebrew](), [laravel](), [mysql](), [phoenix]() ### AI overview The author sets aside Elm after finding a simple HTML form frustrating to implement and experiments with moving a Laravel application to Elixir and Phoenix. The article documents updating Elixir on macOS, installing Phoenix, generating a Phoenix application with MySQL, configuring the database, and adapting migrations for an existing schema. ### Source excerpt In my last blog post, I dug into Elm and while I like a number of things conceptually about Elm, the process of implementing nothing more than a maybe 8 element HTML form left me hugely frustrated and annoyed. I also didn't like the way that Elm bundles code and display into one thing. I may be a traditionalist perhaps but the separation of views and code really does work well in practice. I get that Elm is a different thing but it shouldn't be this hard to just put some text and an html form on the screen. And, so, I'm putting Elm to the side for a bit and going to experiment with using Elixir and Phoenix for my previous Laravel application. If nothing else this should be much more straightforward as it is moving from one MVC style framework to another albeit from an OO lang (php) to a functional lang (elixir). Step 1: Getting Up To Date I'm on OSX and my goal was to get to the current Elixir and Phoenix before I started, This I found to be surprisingly problematic. And, perhaps, it was my fault as I don't claim to be great with HomeBrew. I started with: brew update brew install elixir@1.12 But no matter what I did, I couldn't get past elixir 1.11. So my next step was to get rid of everything. Getting Rid of Everything I started with: brew uninstall elixir And then I got a warning about a shallow copy issue which told me to run: git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow brew update brew install elixir which finally resulted in: ❯ elixir -v Erlang/OTP 24 [erts-12.3.1] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit] [dtrace] Elixir 1.13.3 (compiled with Erlang/OTP 24) Installing Phoenix A bit of googling gave me this command to install the newest Phoenix: mix archive.install hex phx_new Step 2: Generating a New App Although I've actually been to ElixirCon, things have changed a lot in a few years. Here's the new syntax for generating an app: mix phx.new kit_selector3 --database mysql Normally I'd be using pos ## Supabase Realtime, with Multiplayer Features DevFeed: [Supabase Realtime, with Multiplayer Features]() Original publisher: [Read original article]() Author: Wen Bo Xie Published: 2022-04-01T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [WebSocket](), [Multitenancy](), [distributed-systems](), [Concurrency](), [Databases](), [Streaming](), [Elixir](), [phoenix]() Tags: [apps](), [architecture](), [concurrency](), [databases](), [developers](), [elixir](), [extension](), [features](), [multi-tenancy](), [phoenix](), [postgresql](), [streaming]() ### AI overview Supabase announces a new version of Realtime that adds multiplayer capabilities alongside existing PostgreSQL change streaming. The release introduces multi-tenancy, distributed clusters, presence, broadcast messaging, and a more extensible WebSocket architecture for games and collaborative applications. ### Source excerpt Today we're announced Realtime, with multiplayer features. Realtime enables broadcast, presence, and listening to database changes delivered over WebSockets. ## Standalone CLI: Use Tailwind CSS without Node.js DevFeed: [Standalone CLI: Use Tailwind CSS without Node.js]() Original publisher: [Read original article]() Published: 2021-12-16T16:00:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Node.js](), [Web Development](), [modern web development]() Tags: [cli](), [css](), [github](), [javascript](), [node-js](), [phoenix](), [rust](), [tailwind](), [vercel]() ### AI overview Tailwind CSS announces a standalone CLI executable that provides Tailwind CLI without requiring Node.js or npm. It packages the Node.js project with pkg while retaining JavaScript configuration support and includes first-party plugins. ### Source excerpt Today we're announcing a new standalone CLI build that gives you the full power of Tailwind CLI in a self-contained executable -- no Node.js or npm required. ## Taking Another Look at Phoenix and Elixir - Part 1 - Upgrading DevFeed: [Taking Another Look at Phoenix and Elixir - Part 1 - Upgrading]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-15T14:23:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Elixir](), [phoenix](), [Homebrew](), [Package manager](), [Erlang](), [Rails]() Tags: [elixir](), [erlang](), [homebrew](), [installation](), [phoenix](), [rails](), [tooling](), [upgrade]() ### AI overview A practical guide to upgrading Elixir, Erlang/OTP, Mix, Hex, and Phoenix, then creating a sample Phoenix application and preparing to compare it with an existing Rails codebase. ### Source excerpt I've been on the fence about Phoenix and Elixir for a while and I thought I'd take at least a quick dive. I've had a development system for Phoenix and Elixir since at least 2016 but I haven't done much. This means that the first task is bringing it into the 2020s. Upgrading Elixir I installed Elixir via HomeBrew which means it is a simple: which elixir /usr/local/bin/elixir Note: It can be hard sometimes to know if you installed things via HomeBrew and checking their location is an easy cheap as HomeBrew installs stuff to /usr/local/bin And then: brew upgrade elixir And then: elixir --version Erlang/OTP 23 [erts-11.0.3] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [hipe] [dtrace] Elixir 1.10.4 (compiled with Erlang/OTP 23) You can also use just -v: elixir -v Erlang/OTP 23 [erts-11.0.3] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [hipe] [dtrace] Elixir 1.10.4 (compiled with Erlang/OTP 23) Upgrading Mix and Hex Mix and Hex give the equivalent of a build tool (like Rake from the Rails world) and a Package Manager (like Gem / Bundler). To upgrade mix, you use: mix local.hex Found existing entry: /Users/sjohnson/.mix/archives/hex-0.20.5 Are you sure you want to replace it with "https://repo.hex.pm/installs/1.10.0/hex-0.20.5.ez"? [Yn] Y * creating /Users/sjohnson/.mix/archives/hex-0.20.5 And that will upgrade both mix and hex. Upgrading Phoenix The phoenix framework version I have dates back to 1.2 or 1.3 I think. The first step is to figure out what version I have: mix phoenix.new --version Phoenix v1.3.3 The method to upgrade the Phoenix framework itself is: mix archive.install hex phx_new 1.5.4 I used a google query to discover that the current Phoenix framework version was 1.5.4. The other way to find this version number is to go to this url: https://hexdocs.pm/phoenix/installation.html And then look at the drop down of different versions in the left hand sidebar. The latest version is always at the top. Creating a Sample App My fir ## Apache Phoenix Connector DevFeed: [Apache Phoenix Connector]() Original publisher: [Read original article]() Author: Vincent Poon Published: 2019-06-04T00:00:00Z Content type: release Language: en Sources: [Trino Blog]() Topics: [phoenix](), [data](), [Query (disambiguation)](), [configuration](), [Framework](), [Structured-data]() Tags: [apache](), [clusters](), [configuration](), [data](), [feature](), [framework](), [integration](), [map](), [operations](), [phoenix](), [schema]() ### AI overview Presto 312 introduces an Apache Phoenix Connector for querying HBase data through Apache Phoenix. It supports federation across multiple Phoenix clusters, joins with other Presto data sources, and complex operations such as aggregations and joins handled by the Presto engine. ### Source excerpt Presto 312 introduces a new Apache Phoenix Connector, which allows Presto to query data stored in HBase using Apache Phoenix. This unlocks new capabilities that previously weren't possible with Phoenix alone, such as federation (querying of multiple Phoenix clusters) and joining Phoenix data with data from other Presto data sources. ## Release 312 DevFeed: [Release 312]() Original publisher: [Read original article]() Published: 2019-05-29T00:00:00Z Content type: release Language: en Sources: [Trino Blog]() Topics: [releases]() Tags: [apache](), [bug](), [mysql](), [optimization](), [performance](), [phoenix](), [postgresql](), [release](), [release-notes](), [support]() ### AI overview Release 312 adds performance improvements, UUID support, an Apache Phoenix connector, expanded PostgreSQL and MySQL data-type support, Hive bucketed-table improvements, and bug fixes. ### Source excerpt This version has many performance improvements (including cast optimization), a new UUID data type and uuid() function, a new Apache Phoenix connector, support for the PostgreSQL TIMESTAMP WITH TIME ZONE data type, support for the MySQL JSON data type, improved support for Hive bucketed tables, and some bug fixes. Release notes Download ## Omid 1.0.0 adds low-latency transaction processing for Apache Phoenix DevFeed: [Omid 1.0.0 adds low-latency transaction processing for Apache Phoenix]() Original publisher: [Read original article]() Author: amberwilsonla-blog Published: 2018-12-06T19:32:04Z Content type: release Language: en Sources: [Yahoo]() Topics: [phoenix](), [Transactions](), [Hadoop](), [SQL](), [Deployment](), [Cloud]() Tags: [big-data](), [cloud](), [deployment](), [hadoop](), [low-latency](), [open-source](), [phoenix](), [real-time](), [speed](), [sql](), [transactions](), [yahoo-engineering]() ### AI overview This release article introduces Omid 1.0.0, an open source transaction processing platform for Big Data, and announces its selection as the transaction management provider for Apache Phoenix. It describes the Omid Low Latency protocol, which reduces short-transaction latency by 5 times under light load and by 10 to 100 times under heavy load. ### Source excerpt yahoodevelopers: By Ohad Shacham, Yonatan Gottesman, Edward Bortnikov Scalable Systems Research, Verizon/Oath Omid, an open source transaction processing platform for Big Data, was born as a research project at Yahoo (now part of Verizon), and became an Apache Incubator project in 2015. Omid complements Apache HBase, a distributed key-value store in Apache Hadoop suite, with a capability to clip multiple operations into logically indivisible (atomic) units named transactions. This programming model has been extremely popular since the dawn of SQL databases, and has more recently become indispensable in the NoSQL world. For example, it is the centerpiece for dynamic content indexing of search and media products at Verizon, powering a web-scale content management platform since 2015. Today, we are excited to share a new chapter in Omid's history. Thanks to its scalability, reliability, and speed, Omid has been selected as transaction management provider for Apache Phoenix, a real-time converged OLTP and analytics platform for Hadoop. Phoenix provides a standard SQL interface to HBase key-value storage, which is much simpler and in many cases more performant than the native HBase API. With Phoenix, big data and machine learning developers get the best of all worlds: increased productivity coupled with high scalability. Phoenix is designed to scale to 10,000 query processing nodes in one instance and is expected to process hundreds of thousands or even millions of transactions per second (tps). It is widely used in the industry, including by Alibaba, Bloomberg, PubMatic, Salesforce, Sogou and many others. We have just released a new and significantly improved version of Omid (1.0.0), the first major release since its original launch. We have extended the system with multiple functional and performance features to power a modern SQL database technology, ready for deployment on both private and public cloud platforms. A few of the significant innovations include: Protocol ## Gradient and Image Background on FloatingActionButton DevFeed: [Gradient and Image Background on FloatingActionButton]() Original publisher: [Read original article]() Author: Shai Almog Published: 2016-11-01T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [phoenix](), [Material Design]() Tags: [component](), [design](), [material-design](), [phoenix]() ### AI overview This article explains an added FloatingActionButton mode in the Phoenix theme that uses the parent UIID to draw a gradient or image background. It notes that round-shape clipping has performance and port-compatibility limitations, so the behavior is disabled by default. ### Source excerpt The Phoenix theme had a FloatingActionButton with a gradient on top. This goes against the mostly flat material design spec but after looking at the design with a solid color I came to the conclusion that the designer was totally right to use a gradient in this case. Unfortunately we didn't build that support into the FloatingActionButton. So as part of that work I added a special mode to the RoundBorder that uses the parent UIID to draw the background. This sounds like a "no brainer" but there is a catch: the round border needs to be "round". ## Template - Phoenix UI DevFeed: [Template - Phoenix UI]() Original publisher: [Read original article]() Author: Shai Almog Published: 2016-10-31T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [phoenix](), [Template](), [ui](), [GUI](), [JavaScript](), [Android]() Tags: [android](), [code](), [design](), [gui](), [javascript](), [phoenix](), [ui]() ### AI overview This article describes adapting Adrian Chiran's Phoenix UI kit into a cross-platform demo. It discusses portability issues between devices and the JavaScript port, use of the GUI builder, and challenges adapting the rounded walk-through interface across screen densities and orientations. ### Source excerpt The Phoenix UI kit by Adrian Chiran is one of the best looking and most challenging template UI's I had to adapt in recent history. The breadth of the design is pretty challenging but it also has some elements that are really hard to adapt across platforms in a portable way. In fact, some elements only work on devices and don't even work properly for the JavaScript port e.g. the floating action button gradient color and the round look of the walkthru UI.