# Elixir Elixir is a programming language for building scalable, fault-tolerant software systems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## App Engine Flex Language Shootout DevFeed: [App Engine Flex Language Shootout]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-04-17T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Hackathon](), [Back end](), [Elixir](), [distributed-systems](), [Open Source]() Tags: [backend](), [distributed-systems](), [elixir](), [engineering](), [hackathon](), [infrastructure](), [news](), [open-source]() ### AI overview A first-person account of a Khan Academy hackathon project exploring Google App Engine Flex and comparing programming-language options. The author describes Khan Academy's existing Python backend, interest in gaining experience with Flex, and personal interest in Elixir, while noting that a language switch was not imminent. ### Source excerpt By Amos Latteier This is the second time I've been to Silicon Valley. Some years ago - never ... Read more ## Security updates for Monday DevFeed: [Security updates for Monday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-14T13:18:14Z Content type: news Language: en Sources: [LWN.net]() Topics: [Security](), [Debian](), [Fedora](), [Firefox](), [Git](), [nginx](), [Python](), [cURL](), [Elixir](), [F#](), [Redis](), [Rust]() Tags: [curl](), [debian](), [elixir](), [firefox](), [git](), [nginx](), [python](), [redis](), [rust](), [security](), [updates]() ### AI overview Security updates were issued across AlmaLinux, Debian, Fedora, Gentoo, Mageia, Oracle, and SUSE. The affected software includes operating-system components, browsers, developer tools, programming-language packages, servers, libraries, and cloud-related utilities. ### Source excerpt Security updates have been issued by AlmaLinux (389-ds-base, apr-util, coreutils, freerdp, git-lfs, glib2, gstreamer1-plugins-base, kernel, libkcapi, nginx, nodejs:22, nodejs:24, osbuild-composer, perl-YAML-Syck, postgresql16-postgis, ruby, ruby4.0, ruby:3.3, and vim), Debian (jbig2dec, kamailio, nginx, spip, and xorg-server), Fedora (baresip, bind, bluez, bubblewrap, chirp, chromium, cockpit, composer, corosync, darktable, dokuwiki, elixir, exiv2, expat, firefox, freerdp, freerdp2, gdk-pixbuf2, gegl04, golang-x-perf, grpcurl, kernel, kernel-headers, libevent, libmongocrypt, libpcap, libre, libsoup3, memcached, mingw-expat, mingw-openexr, mongo-c-driver, mrtg, nagios-plugins, nsd, nss, openssl, openvpn, PackageKit, pdns-recursor, perl-Net-OAuth, perl-XML-Bare, php-pecl-mongodb2, python-asteval, python-pip, rclone, rest, rust-hickory-net, rust-hickory-proto, rust-hickory-resolver, rust-ppmd-rust, rust-webbrowser, srt, syncthing, tar, tkimg, and valkey), Gentoo (Chromium, Google Chrome, Microsoft Edge, Opera, Vivaldi and Ruby), Mageia (bind, ffmpeg, glibc, java-17-openjdk, java-21-openjdk, librabbitmq, perl-Catalyst-Plugin-Static-Simple, perl-Imager, tor, and xz), Oracle (389-ds:1.4, ansible-core, apr-util, coreutils, freerdp, git-lfs, glib2, gstreamer1-plugins-base, gzip, httpd:2.4, image-builder, java-21-openjdk, kernel, mrtg, nginx, osbuild-composer, perl-DBI, postgresql16-postgis, python-lxml, python3.12-lxml, redis:6, and vim), SUSE (389-ds, ansible-core, ansible-creator, azure-storage-azcopy, cargo-audit, chromedriver, chromium, clamav, containerized-data-importer1.65, containerized-data-importer1.66, curl, dracut, ffmpeg-4, google-guest-agent, google-osconfig-agent, helm, java-1_8_0-ibm, jupyter-nbconvert, kernel, libpng16, libusb-1_0, libvirt, multipath-tools, NetworkManager, opensc, openssl-3, perl-Authen-SASL, perl-HTML-FormHandler, perl-Mojolicious, perl-Protocol-HTTP2, python-jwcrypto, python-sqlparse, python-tornado6, python313-geopy, python313-modelscope ## How Discord Added Distributed Tracing to Its Elixir Message-Passing Services DevFeed: [How Discord Added Distributed Tracing to Its Elixir Message-Passing Services]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-05-18T15:39:51Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [Discord](), [Elixir](), [tracing](), [Traces](), [telemetry](), [gRPC]() Tags: [discord](), [elixir](), [messages](), [traces](), [tracing]() ### AI overview The article describes Discord's distributed-tracing implementation for Elixir services that communicate through message passing. It highlights trace-context propagation through message envelopes, a gradual zero-downtime migration, fanout-based sampling, lazy context unpacking, and restrictions on root spans after fanout. ### Source excerpt PLUS: AI as Netflix model ๐Ÿ“Š, Spotify NLI via Claude ๐ŸŽต, Subagent patterns 2026 ๐Ÿค– ## 100,000 GitHub stars DevFeed: [100,000 GitHub stars]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2026-04-02T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Open Source](), [Databases](), [GitHub](), [Deno](), [Elixir](), [API](), [Embeddings]() Tags: [community](), [database](), [developers](), [discord](), [elixir](), [embeddings](), [github](), [open-source](), [tool]() ### AI overview Supabase celebrates reaching 100,000 GitHub stars and says eight million developers are building with the platform. The article reflects on its open-source, community-focused approach and highlights projects supporting Supabase, including Postgres, PostgREST, pgvector, Deno, imgproxy, and Elixir Phoenix. ### Source excerpt Supabase hits 100,000 GitHub stars. A reflection on community, open source, and what got us here. ## Tracing Discord's Elixir Systems (Without Melting Everything) DevFeed: [Tracing Discord's Elixir Systems (Without Melting Everything)]() Original publisher: [Read original article]() Author: Nick Krichevsky Published: 2026-03-04T00:00:00Z Content type: article Language: en Sources: [Discord Blog]() Topics: [tracing](), [Elixir](), [Discord](), [Concurrency](), [observability](), [Instrumentation](), [systems]() Tags: [concurrency](), [concurrent](), [discord](), [elixir](), [instrumentation](), [logs](), [metrics](), [monitoring](), [observability](), [on-call](), [outage](), [systems](), [tracing]() ### AI overview Discord describes how it added distributed tracing to its Elixir systems to investigate guild performance problems and outages at scale. The article explains the limitations of metrics, logs, and the internal guild timings tool, then outlines the work required to propagate tracing information through Elixir's message-passing system. ### Source excerpt Join Senior Software Engineer Nick Krichevsky as he explains how Discord added distributed tracing to Elixir's message passing and optimized it to handle millions of concurrent users. ## Scaling Whatnot: Behind the Largest Live Shopping Stream in US History DevFeed: [Scaling Whatnot: Behind the Largest Live Shopping Stream in US History]() Original publisher: [Read original article]() Author: Whatnot Engineering Published: 2026-02-24T14:33:16Z Content type: article Language: en Sources: [Whatnot Engineering]() Topics: [Scalability](), [Architecture & Design](), [Platform Engineering](), [SRE](), [Elixir](), [Python]() Tags: [cloud-computing](), [devops](), [elixir](), [infrastructure](), [load-testing](), [python](), [resilience](), [scalability](), [scale](), [site-reliability-engineer](), [software-engineering](), [sre](), [technology]() ### AI overview Whatnot describes how it prepared its platform for a MrBeast giveaway stream that reached 583,000 concurrent viewers and became the largest live shopping event in US history. The article covers architectural investments, progressive production load testing, event-day results, and lessons for future scalability. ### Source excerpt On February 8, 2026, over a half million viewers tuned in to watch MrBeast give away 1 million dollars in prizes on Whatnot. On Big Game Sunday 2026, MrBeast went live on Whatnot for a giveaway show that would become the largest live shopping event in US history. At peak, 583,000 concurrent viewers were watching a single show on our platform. Over 555k people entered a single giveaway. We drove hundreds of thousands of new signups in 24 hours. If any one of a dozen systems buckled, it would have happened live on camera. We pulled it off with zero major incidents. But that outcome was never guaranteed. It took months of preparation, 60+ engineers across every major engineering org, and some of the most significant infrastructure investments we've ever made. In this post, we'll walk through the biggest technical challenges we faced and how we solved them, not with throwaway scaffolding, but with durable platform improvements that raise our scalability ceiling for every seller and buyer on the platform. We'll cover the work in three parts. First, the key architectural investments we made to handle this scale: admission control, connection pooling, feed resilience, and video infrastructure. Then, how we validated it all through progressive production load testing. Finally, what happened on event day, what we learned, and what we're carrying forward. Setting the Stage If you've followed our blog, you might remember our Post Malone "Post-Poned" post from 2022 or our three-part series on preparing for the 2024 Big Game. Each of those events pushed us to improve, and each one revealed new limits. As our community has grown, scaling our infrastructure to match has been a consistent priority. The MrBeast event was on a different order of magnitude entirely, but it accelerated work that was already underway. Our target was to support 1 million concurrent viewers on a single stream and 1.35 million across the platform. To put that in perspective, our previous largest event had ## Building a MCP Server in Elixir DevFeed: [Building a MCP Server in Elixir]() Original publisher: [Read original article]() Author: Vinicius Negrisolo Published: 2025-11-25T14:00:00Z Content type: tutorial Language: en Sources: [Hashrocket]() Topics: [MCP Server](), [Model Context Protocol](), [Elixir](), [API](), [Tool](), [Documentation]() Tags: [ai](), [api](), [building](), [development](), [documentation](), [elixir](), [mcp](), [mcp-server](), [model-context-protocol](), [process](), [tool]() ### AI overview A practical guide to building an MCP server in Elixir for a TIL website. The project uses Anubis to expose a tool that creates TIL posts from AI tooling, with detailed tool and input descriptions to help the AI map requests to the expected schema. ### Source excerpt We've been working with MCP servers for a while, and this use case was a perfect opportunity to build out another one. What is an MCP Server? A very simple way to put it is that Model Context Protocol is an "API" that your AI tooling can use to get external data or perform actions by interacting with your application. If it's just an API, that seems very easy to implement. Let's think about our use case then. The Use Case The project is the TIL https://til.hashrocket.com/ website where we developers usually write about our own learning experiences throughout small TIL posts. So our idea with the MCP server was to provide a way to simply create a TIL post from inside our AI tooling, and then maybe go to the TIL site and refine that idea. These days we spend a lot of time inside our AI tools asking the most variety of questions, and we end up learning something from those interactions. Eventually, if we learn from an AI chat interaction, we'd like to just grab that content and maybe scaffold it into a new TIL post. This was the starting point of the project, and with that we started to take a look into libraries to achieve that. We found out that there were 2 libraries that were both forks of each other: Hermes MCP Anubis MCP We played around a bit with Hermes but we ended up using Anubis in the end. I have to say it was a bit of a bumpy road. The documentation for both was not the best - we had some situations where the documentation was outdated or just simply not working - so follow our steps here if you want to setup an MCP server yourself. MCP Server The first component to write is an MCP server, which is very simple. For now it's just: defmodule Tilex.MCP.Server do use Anubis.Server, name: "TIL", version: "1.0.0", capabilities: [:tools] component(Tilex.MCP.NewPost) end MCP Tools So the first tool we made was to create a TIL Post: defmodule Tilex.MCP.NewPost do @moduledoc """ Create a new TIL ("Today I Learned") post. TIL is a place for sharing something you've l ## 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 ## AI GPU Clusters, From Your Laptop, With Livebook DevFeed: [AI GPU Clusters, From Your Laptop, With Livebook]() Original publisher: [Read original article]() Published: 2024-09-24T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [Elixir](), [fly.io](), [jupyter](), [Cloud](), [Machine learning](), [Serverless](), [GPU](), [PyTorch]() Tags: [access-control](), [ai](), [ai-and-ml](), [cdn](), [close-to-users](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [gpu](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [infrastructure](), [jupyter](), [networking](), [postgresql-clusters](), [serverless](), [servers]() ### AI overview This recap introduces Livebook, FLAME, and the Nx stack as Elixir components for interactive notebooks, elastic code execution, and Elixir-native AI and machine learning. It describes moving computation between a laptop and remote Fly.io infrastructure, including GPU-backed workloads, and discusses private network access to other applications such as databases. ### Source excerpt Livebook, FLAME, and the Nx stack: three Elixir components that are easy to describe, more powerful than they look, and intricately threaded into the Elixir ecosystem. A few weeks ago, Chris McCord (๐Ÿ‘‹) and Chris Grainger showed them off at ElixirConf 2024. We thought the talk was worth a recap. Let's begin by introducing our cast of characters. Livebook is usually described as Elixir's answer to Jupyter Notebooks. And that's a good way to think about it. But Livebook takes full advantage of the Elixir platform, which makes it sneakily powerful. By linking up directly with Elixir app clusters, Livebook can switch easily between driving compute locally or on remote servers, and makes it easy to bring in any kind of data into reproducible workflows. FLAME is the Elixir's answer to serverless computing. By having the library manage a pool of executors for you, FLAME lets you treat your entire application as if it was elastic and scale-to-zero. You configure FLAME with some basic information about where to run code and how many instances it's allowed to run with, and then mark off any arbitrary section of code with Flame.call. The framework takes care of the rest. It's the upside of serverless without committing yourself to blowing your app apart into tiny, intricately connected pieces. The Nx stack is how you do Elixir-native AI and ML. Nx gives you an Elixir-native notion of tensor computations with GPU backends. Axon builds a common interface for ML models on top of it. Bumblebee makes those models available to any Elixir app that wants to download them, from just a couple lines of code. Here is quick video showing how to transfer a local tensor to a remote GPU, using Livebook, FLAME, and Nx: Let's dive into the keynote. Poking a hole in your infrastructure Any Livebook, including the one running on your laptop, can start a runtime running on a Fly Machine, in Fly.io's public cloud. That Elixir machine will (by default) live in your default Fly.io organization, giving ## Nix Weekly Recap: 2024-05-26 DevFeed: [Nix Weekly Recap: 2024-05-26]() Original publisher: [Read original article]() Published: 2024-05-26T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Elixir](), [JSON Schema](), [Neovim](), [modules]() Tags: [elixir](), [modules](), [recap](), [updates](), [weekly]() ### AI overview A weekly recap covering the final steps toward the NixOS 24.05 release, a Constitutional Assembly Q&A, the deps_nix Elixir builder, Neovim flake changes, and a tool for extracting JSON Schema definitions from NixOS modules. ### Source excerpt Closing in on NixOS 24.05, Constitutional Assembly Q&A, an improved Elixir builder, Neovim flake updates, and JSON Schemas for NixOS modules. ## Elixir clustering using Postgres DevFeed: [Elixir clustering using Postgres]() Original publisher: [Read original article]() Author: Filipe Cabaรงo Published: 2024-01-09T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Elixir](), [Erlang](), [Supabase](), [Cloud](), [Latency]() Tags: [building](), [cloud](), [elixir](), [hosting](), [how-to](), [latency](), [learn](), [postgres](), [servers]() ### AI overview This article explains Supabase's open-source libcluster Postgres Strategy for connecting multiple Elixir nodes without introducing an additional service. It describes using Postgres NOTIFY and LISTEN to discover nodes, propagate address payloads, and support cluster formation and healing through libcluster. ### Source excerpt Learn about our approach to connecting multiple nodes in Elixir using Postgres ## Supavisor 1.0: a scalable connection pooler for Postgres DevFeed: [Supavisor 1.0: a scalable connection pooler for Postgres]() Original publisher: [Read original article]() Author: Stanislav Muzhyk Published: 2023-12-13T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Elixir](), [SQL](), [Rust](), [Parsing](), [Concurrency](), [IO](), [Transactions](), [Supabase]() Tags: [concurrency](), [elixir](), [load-balancing](), [parsing](), [postgres](), [rust](), [sql](), [transactions]() ### AI overview Supavisor 1.0 is a production-ready Elixir connection pooler for Postgres, adding query load balancing, named prepared statement support, and query cancellation. It uses Rust for efficient SQL parsing and supports high concurrency and rapid I/O. ### Source excerpt Supavisor is now used across all projects, providing a scalable and cloud-native Postgres connection pooler that can handle millions of connections ## Supabase Beta November 2023 DevFeed: [Supabase Beta November 2023]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2023-12-05T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Developer Platform](), [Command-line interface](), [Elixir](), [React Native](), [Retrieval Augmented Generation (RAG)](), [SSL]() Tags: [cli](), [connectivity](), [developer-platform](), [elixir](), [features](), [files](), [hackathon](), [launch](), [open-source](), [postgres](), [rag](), [react-native](), [ssl](), [updates](), [uploads]() ### AI overview Supabase announces Launch Week X and several platform updates, including Resumable Uploads for Pro projects with files up to 50GB, browser-based CLI login, a Postgres strategy for the open source Elixir library libcluster, SSL by default for direct Postgres connections from Edge Functions, configurable session controls, dashboard improvements, and educational resources for AI applications and React Native. ### Source excerpt Launch Week X is coming! But we still have cool updates that we couldn't fit next week. ## Supabase Beta August 2023 DevFeed: [Supabase Beta August 2023]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2023-09-08T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Embeddings](), [hugging face](), [Command-line interface](), [Python](), [OAuth 2.0](), [observability](), [Vercel](), [Elixir](), [Multi-tenancy](), [Next.js](), [Latency]() Tags: [cli](), [elixir](), [embeddings](), [hugging-face](), [integration](), [latency](), [multi-tenancy](), [next-js](), [oauth2](), [observability](), [open-source](), [python](), [recap](), [update](), [vercel](), [web-applications]() ### AI overview Supabase reviews the products and features shipped during Launch Week 8, including faster vector search with pgvector 0.5.0 and HNSW indexes, Hugging Face support, local development upgrades, Supabase branching, Studio 3.0, OAuth2 applications, Vercel Integration 2.0 with Next.js App Router support, and Supavisor for scaling Postgres connections. It also highlights community activity, HIPAA and SOC2 Type 2 compliance, and hackathon winners. ### Source excerpt Launch Week 8 review and more things we shipped ๐Ÿš€ ## Supavisor: Scaling Postgres to 1 Million Connections DevFeed: [Supavisor: Scaling Postgres to 1 Million Connections]() Original publisher: [Read original article]() Author: Egor Romanov; Chase Granberry; Stanislav Muzhyk Published: 2023-08-11T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [benchmarking](), [Elixir](), [Database](), [Multi-tenancy](), [Latency](), [k6](), [Terraform](), [Grafana](), [Prometheus](), [Amazon EC2](), [Amazon Web Services]() Tags: [arm](), [aws](), [benchmarking](), [caching](), [cloud-native](), [elixir](), [grafana](), [k6](), [latency](), [load-balancing](), [multi-tenancy](), [postgres](), [prometheus](), [terraform](), [ubuntu]() ### AI overview Supavisor is a scalable, cloud-native Postgres connection pooler built in Elixir for multi-tenant workloads. Supabase benchmarked it under load and reports support for up to one million concurrent connections, with a single 16-core instance reaching 250,000 connections and processing 20,000 queries per second in the described baseline test. ### Source excerpt Supavisor is a scalable, cloud-native Postgres connection pooler. We connected a million clients to it to see how it performs. ## This Week at Zed: Parsing, PHP Syntax Highlighting, Tree-sitter, and UI Updates DevFeed: [This Week at Zed: Parsing, PHP Syntax Highlighting, Tree-sitter, and UI Updates]() Original publisher: [Read original article]() Author: Kirill Bulatov Published: 2023-07-14T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Parsing](), [Tree-sitter](), [Syntax Highlighting](), [Code generation](), [PHP](), [Ruby](), [Elixir](), [Svelte]() Tags: [code-generation](), [elixir](), [parsing](), [php](), [programming](), [ruby](), [svelte](), [syntax](), [ui]() ### AI overview A weekly Zed development update covering fixes to parsing disjoint ERB and HEEx code ranges, language-specific editing behavior, PHP syntax highlighting and LSP integration, Tree-sitter code-generation improvements, and several UI updates. The update also reports reducing tree-sitter-rust compile time from 30 seconds to 6 seconds. ### Source excerpt Quiet weeks bring fruits. ## This Week at Zed Industries: #7 DevFeed: [This Week at Zed Industries: #7]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-06-16T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Development](), [Open Source](), [ide](), [Artificial Intelligence](), [dashboards](), [Elixir](), [Cloudflare](), [OpenAI](), [Vercel](), [datadog]() Tags: [ai](), [code](), [development](), [elixir](), [open-source](), [other]() ### AI overview A weekly update from Zed Industries covering plans to open-source Zed on Zed, project-specific settings in v0.90.1, Elixir development improvements, assistant-panel work, inlay hints, analytics tooling, and an unresolved reporting bug involving Cloudflare Workers, OpenAI, Vercel logging, and DataDog. ### Source excerpt We're open-sourcing Zed on Zed and adding an AI-powered assistant panel! ## This Week at Zed Industries: #6 DevFeed: [This Week at Zed Industries: #6]() Original publisher: [Read original article]() Author: Antonio Scandurra Published: 2023-06-09T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Development](), [Elixir](), [Tree-sitter](), [telemetry](), [Syntax Highlighting](), [observability ai agents](), [OpenAI](), [toolchain](), [configuration]() Tags: [ai-assistants](), [configuration](), [development](), [elixir](), [openai](), [syntax](), [telemetry](), [toolchain]() ### AI overview This weekly Zed development update covers Zed 0.89, including language server protocol support and improvements to the Assistant Panel, panic telemetry, feedback analysis, build configuration, Elixir support, syntax highlighting, and Tree-sitter query reloading. ### Source excerpt We're working on language servers, AI assistants, and plenty more! ## 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. ## Stepping Out Of The Knowledge Zone DevFeed: [Stepping Out Of The Knowledge Zone]() Original publisher: [Read original article]() Published: 2022-04-13T00:00:00Z Content type: opinion Language: en Sources: [Artsy]() Topics: [Elixir](), [Learning](), [Ruby](), [Rails]() Tags: [backend](), [blog](), [blog-post](), [cypress](), [elixir](), [forque](), [front-end](), [horizon](), [integrity](), [learning](), [ruby](), [ruby-on-rails](), [teams](), [velocity]() ### AI overview A first-person reflection on moving beyond familiar Ruby on Rails work and embracing the challenge of learning Elixir. The author connects this transition to Artsy shipping work and a broader willingness to remain open to being a beginner. ### Source excerpt As I am writing my first blog post for Artsy, here is a short introduction on who I am: My name is Kaja and I am an engineer in our Berlin entity. As a Ruby-born programmer I am calling myself a backend engineer, but that also may change and is more about emotional identification and less about what I actually do (as you will see in this blog post). My background is not in engineering at all. In university I graduated in philosophy and historical linguistics, both the most impractical but most beautifully theoretical subjects I can think of. I really love being in the world of ideas and thought experiments that challenge the current status of what is, as opposed to what is thinkable. At Artsy I am currently working in the PX (Partner Experience) Team and since I joined 1 year ago, most of my time in the PX team has been dedicated to the implementation of the Artsy Shipping feature. In the backend I helped tying the ties between the external ARTA-API (a white glove shipping company) and our own service that is managing the shipping and order statuses of the artworks that are ordered online. In the front end I implemented some forms for that feature and some so called hooks. I felt like a fish in the water with these tasks, because the company that I had worked at before was a shipping company and I did the same thing from the other side of the API relationship. In the same language (Ruby on Rails). Here is another fact about me that is a premises for what comes next: I enjoy to be a learner of new things much more than being an expert about things that I already know. Of course being an expert is also flattering the ego, but after a while it can feel repetitive and make your soul feel old and tired. While the experience of being new to something and not an expert at all can give you a rejuvenating prickle. On the other side it can be scary to admit not knowing something and also the ego will feel small and hurt. But I learned that overcoming the hurt ego is my way to ## 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. ## Upgrading Elix on OSX with Brew DevFeed: [Upgrading Elix on OSX with Brew]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-03-22T17:42:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Elixir](), [Homebrew](), [osx]() Tags: [dependency](), [elixir](), [osx](), [packages](), [upgrade]() ### AI overview A short guide to upgrading Elixir on macOS with Homebrew. It shows how to check the installed Elixir version, verify the Homebrew installation, run the upgrade, inspect dependencies, and check the version again. The article notes that upgrading may also update additional packages. ### Source excerpt This is simple but I keep needing to look it up. First check your elixir version: elixir -v Second confirm that you actually installed Elixir using brew: brew list | grep elixir Third do the upgrade: brew upgrade elixir Note: You are probably going to find more than just elixir itself is upgraded. Theoretically you should be able to look at just the upgrade tree with: brew deps --tree --include-build elixir and only those things will be upgraded but when I noted a much larger group of packages being upgraded which makes me suspect some kind of circular dependency that needed to be handled. Fourth check the version again: elixir -v ## Workflows are coming to Supabase DevFeed: [Workflows are coming to Supabase]() Original publisher: [Read original article]() Author: Francesco Ceccon Published: 2021-04-02T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Orchestration](), [Elixir](), [Open Source](), [Databases](), [AWS Step Functions](), [Serverless]() Tags: [api](), [aws](), [aws-step-functions](), [azure](), [cloudflare-workers](), [database](), [elixir](), [gcp](), [open-source](), [orchestration](), [serverless](), [workflows]() ### AI overview Supabase describes Workflows as an open-source orchestration engine intended to complement its Functions offering. The planned Elixir-based engine will manage complex workflows, queueing, and coordination of existing functions across cloud platforms and Postgres, with deep Postgres integration and SQL-accessible state. ### Source excerpt Functions are great, but you know what's better? [Next page]()