Tidewave

Tidewave is the coding agent for full-stack web app development, deeply integrated with Phoenix, from the database to the UI. See our website for more information.

A recent study by Tencent showed that Elixir had the highest completion rate across models when compared among 20 different programming languages. When combining the results of all 30+ evaluated models, 97.5% of Elixir problems were solved by at least one model, the highest among all languages:

timeseries , ecto & postgresql

Phoenix LiveView Calendar with Drag-and-Drop

Markdown for Elixir _

Fast. Extensible. Phoenix-native. AI-ready.

An Elixir program consist of a large number of lightweight, concurrent processes communicating with each other via asynchronous messages. A process receives and handles incoming messages, transforming its internal state in a functional way. Inside a process, all code is sequential. The VM running Elixir, BEAM, normally utilizes all cores of a modern CPU and schedules processes for execution. By running many concurrent processes you can maximize the performance of current hardware.

When you're selling stuff, every click away from your website is a potential lost sale. Customers kept asking us to allow people to buy tickets without leaving their branded site. They loved the service, but wanted to retain brand presence and coherence.

The ask seemed simple enough. Drop a widget on any webpage, show some events, let people check out. But as we dug into it, the technical challenges started stacking up. How do you maintain cart state across page refreshes? How do you track marketing attribution when the purchase happens on someone else's domain? And how do you process payments securely in what is essentially a third party context?

This is the quick post of how we tried a bunch of approaches, hit walls, and eventually landed on Phoenix Channels as our solution.

Your Python Stack Can’t Do This

Free link here

The AI industry has a “Python Problem.”

While Python dominates model development, it’s catastrophically unsuited for agent orchestration. If you’re building an “Agent Swarm” with LangChain or AutoGPT on a Python backend, you’re fighting the Global Interpreter Lock (GIL), memory bloat, zombie processes, and concurrency nightmares.

I built a platform that actually scales. Using Elixir and the BEAM VM, I orchestrated millions of stateful, autonomous agents on a single cluster, with sub-millisecond message passing, automatic fault recovery, and zero external message queues.

Asynchronous Tasks and Streaming UIs in Phoenix Liveview

The Top 3 LiveView Form Mistakes (And How to Fix Them)
John Curran •
November 07, 2025

I’ve been writing LiveView since 2020. In that time, I’ve seen the same three form mistakes at multiple companies. Here’s what they are and how to fix them.

1. Slow, laggy forms with scattered logic because form state gets stored in socket assigns and server round-trips get used for dynamic UI (conditional inputs, toggles), instead of keeping that state in hidden form inputs where it belongs.

2. Brittle system where UI and database can’t evolve independently because database schemas get used directly for forms, coupling persistence logic to presentation.

3. Users stuck with valid data but can’t submit because changesets get manually manipulated with Map.put or Map.merge instead of Ecto.Changeset functions, leaving stale errors behind.

The common thread: don’t fight the framework. Keep form state on the client, create embedded schemas for your forms, and use Ecto.Changeset functions to modify changesets.

Hot code upgrades for Elixir and Phoenix apps

BEAM OTP: Why Everyone Keeps Reinventing It

What makes BEAM and OTP different from async/await, threads, and actors. Process isolation, supervisors, and why Erlang's model keeps winning 40 years later.

no-agents.md - Le fichier qui dit non aux IA dans votre code
7 mars 2026
/ PAR KORBEN ✨ / 2 MIN DE LECTURE /

IA POUR DÉVELOPPEURSVIE PRIVÉE & ANONYMAT

Ce qu’il faut retenir

no-agents.md est un fichier standard que les agents IA (Copilot, Cursor, Warp) lisent pour savoir comment interagir avec votre code. Ross Baker a créé une version qui interdit TOUT : lecture, analyse, modification, entraînement.
60 000 projets open source utilisent déjà AGENTS.md. Copier le fichier no-agents.md à la racine de votre repo suffit à bloquer les agents respectueux de la spec, sans configuration supplémentaire.
Le bonus CLAUDE.md est un troll intentionnel : Claude ignore la spec AGENTS.md, donc le fichier contient une fausse instruction lui ordonnant de "dormir trois siècles". C'est symbolique mais ça envoie le message.

ny port 8000 sudo ufw route allow proto tcp from any to any port 8443

Introduction

So you want to deploy your Phoenix app. You head to the docs, and in typical Elixir fashion you find a number of thorough and well-written guides. Unfortunately, they're all guides for deploying to cloud PaaS platforms. Well, there is a Releases guide, but it only teaches you how to build a release. Not how to deploy it!

But what if you want to deploy to an actual server? Maybe you want to avoid vendor lock-in, or maybe you just want to manage your own system. You know, like the good old days. This is an opinionated guide for deploying an Elixir/Phoenix app to an actual server. VPS, bare metal - it doesn't matter. Just a server.

Nothing here is novel, but there aren't really any guides that spell it out.

I am going to spell it out.

Transfer podman images without registry

titre

conventional: comments

Comments that are easy to grok and grep