Tjaco Oostdijk retweeted
I'm co-organising the Erlang/Elixir/Gleam devroom at FOSDEM'27 this year, and the call for talks just opened! Looking forward to your submissions 😃 beam-fosdem.dev/ #beam #erlang @elixirlang @gleamlang
Tjaco Oostdijk retweeted
Announcing: Moatless 😎
moatless.store/blog/announci…
Tjaco Oostdijk retweeted
We have a new AI policy for #AshFramework. github.com/ash-project/.gith…
Basically removing all special provisions and replacing them with only one AI-specific rule.
Tjaco Oostdijk retweeted
with all the dunking on @elixirlang, a quick note from someone who bet on it.
phoenix liveview is processes all the way down. that is what lets us build interactive ui without the overhead and indirection of client side state management. we ship and test interfaces insanely fast and nothing else has come close.
and that is just liveview. @elixirphoenix is one of the most productive web stacks i have tried.
the erlang runtime is the other half. agents can attach to it in dev and in prod and see the process tree, memory and cpu, not just symbols. it is a system you can interrogate.
we have not used everything it can do because we have not needed it yet. when something does need to be fast we can drop into a nif and write that part in rust, and so far that has barely come up. we optimized for feeling productive so we could get the business off the ground. @marekfort and i say the same thing every time. best decision we made, and even better with agents.
Tjaco Oostdijk retweeted
To whom it may concern 🙃️
In abstract terms, I think of a software system (e.g. a web server, database, message queue, ...) as a collection of dynamic activities. Multiple things are happening: handling of requests, background tasks, periodical jobs, error handling, reporting, and recovery. Many of this things are completely independent, but some of them are working together.
These activities have their lifecycles. We want to be able to start the activities in the proper order. We want to be able to dynamically start more activities. We want to be able to stop the activities in the reverse order. If Bar depends on Foo, we want to start Foo first, Bar second, and we want to stop them in the reverse order. Some activities will be decomposed into smaller subactivities. So if Foo internally runs Bar and Baz, we want to be able to stop the entire subtree. For example, if a user hits the cancel button, we want to be able to stop all the activities related to that task. And we want to be able to do this even if the task is stuck in some CPU processing loop.
A software system has non-binary success semantics. Just because something fails, doesn't mean everything should stop working. But whatever is tightly coupled to the failing activity should stop too. However, the failing thing should not leave inconsistent mess (state, dangling resources) behind.
BEAM & OTP is give us the primitives that address just that. The way I think about my systems in abstract maps very closely to the way I implement them. This vastly reduces the mental overload of thinking about the code. The conceptual view of the system maps very closely to the actual physical model (process structure). This is a power of a good abstraction. For more details, see my talk Soul of Erlang and Elixir, where I tried to explain the underlying ideas.
The conceptual properties I mentioned above will have to be supported, because they are inherent to a software system. If you're building a software system without this support, these concerns will get entangled with your business logic. Whether you're doing it manually or vibe it, this work becomes more complicated. You or your agent have to deal with non-functional requirements together with the functional ones. This will make your job and the jobs of agents more difficult. Remember: code is the part of the context, perhaps its largest part.
So in the age of agentic development, my position about BEAM remains the same. If you're building a software system, it is the tool that fits the problem, and it will simplify your life. You might bump into situations where some other properties will be more important (e.g. raw processing speed), but you can then implement these parts of your system in another language, say Rust, and manage them from a BEAM-powered system.
As many of you know, I'm a long-time user of Erlang and Elixir. But I don't choose those languages for the syntax. For the record, I actually prefer C-style curly-braces syntax. I use those languages because of the runtime properties and guarantees, and because this technology reduces the impedance mismatch between the way I think about the system and the way I implement it. I also actually mostly prefer Erlang syntax over Elixir (minus some exceptions). The reason why I use Elixir is mostly tooling & some language features (e.g. macros). But the choice of the language was never a fanboy choice for me. If you're not building a system, BEAM langs are most likely not your hammers.
Tjaco Oostdijk retweeted
one shot
Claude Opus 5.5, xHigh reasoning
prompt:
make a dynamic 15 second motion graphics video that shows what an incredible tool tidewave is
Tjaco Oostdijk retweeted
The keynotes at @ElixirConf showed the Elixir community matured a lot when it comes to AI practices within the last year:
* Quinn Wilton discussed the importance and accessibility of applying formal methods and static analysis in the age of AI
* Chris McCord highlighted that last year coding agents could barely run for 20 minutes and today it can run for 20 hours non-stop. You should be stress testing, optimizing, running verifications way more frequently than before. Furthermore, as coding agents own more of the software development cycle, runtime observability becomes part of the loop (something Erlang/Elixir excels at) and will be super valuable (see screenshots)
* Zach Daniel closed with hands on steps to adopt agents throughout and around your software development lifecycle
The keynotes are all on YouTube: youtube.com/@codesync?si=5fw… enjoy!
Tjaco Oostdijk retweeted
Okay, finally back to an #Elixir post! On a Phoenix LiveView project I worked on recently I added a CDN for serving static assets and I'm very happy with it. Phoenix makes this incredibly straightforward, and the result is ⚡
jola.dev/posts/speeding-up-p…
Tjaco Oostdijk retweeted
🥳🎉Today is the day🎉🥳
@hugobarauna, @DimitriKoutmos and I are ready to release Elixir for Finance! We've poured all of our knowledge and know-how into what we believe is one of the best programming+finance books out there 😍.
👉 financialelixir.dev
#ElixirLang #Erlang
Tjaco Oostdijk retweeted
People are sleeping on Elixir for a coding harness:
* Hot-code swapping allows you to build an extensible plugin system similar to Pi, which reloads live without dropping state
* Designing a client-server architecture, similar to OpenCode, is basically a byproduct of the actor model (plus you get both IO/CPU concurrency)
* The built-in distribution means you can easily isolate the brains (model + session) from the hands (sandbox + tools). For example, you can the agentic session on your machine which coordinates agents executing inside Docker or a remote node. Or even have one agent session coordinate multiple nodes (this is basically how Livebook works anyway)
Those can definitely be built from scratch in other languages, but in Elixir the building blocks are basically part of the runtime.
Tjaco Oostdijk retweeted
We have a serious CVE for #AshFramework. If you are using #AshFramework please update to the latest version as soon as you can.
cna.erlef.org/cves/CVE-2026-…
Tjaco Oostdijk retweeted
Sometimes I try to be gentle when it comes to disagreements about technology choices, but I think it is time to start speaking more plainly.
#Elixir, #AshFramework and @elixirphoenix are by a wide margin the best choices to build your business and core technology on top of. If you are building with other things, you're just making a bad decision, plain and simple.
No, that does not mean you are creating a barrier you cannot surmount. We power through bad decisions every day. Yes, there are specific things I wouldn't choose Elixir for. Mobile apps, hard real time number crunching etc. We have some answers for those that I might use if the use case is bounded and I can see that they fit well (NX etc.), but my unqualified "Elixir is better" is less strong in certain domains.
If you are writing a web server, APIs, ETL, etc. there is just flat out no other better option. Fight me bro.
I often say things like "well, I'm biased but ..." when qualifying that one should use Elixir, as I'm the author of #AshFramework, but that framing is getting old. I'm not biased. It's just better technology. I'm happy to debate it, and I don't think that anyone who disagrees with me is stupid, but I do think that they are wrong.
I don't believe in the "different strokes for different folks" thing anymore.
Tjaco Oostdijk retweeted
I had a great chat with @drumusician on why so many musicians become programmers. His answer: it's the same creator itch—you just want to make things you love. Out now on every podcast app: elixirmentor.com/podcast?ep=… #elixirlang #myelixirstatus
Tune in tomorrow!! Looking forward to it!
Live podcast tomorrow! 🎙️
I'm talking with @drumusician (Tjaco Oostdijk), a drummer turned Elixir dev, about going from music to code, building muziekles.app with Claude Code and Tidewave, and keeping Elixir alive at a giant media company that wants Kotlin.
Friday June 5, 10am MT. Come hang out.
elixirmentor.com/events
#ElixirLang #BEAM
2
50
Tjaco Oostdijk retweeted
Elixir v1.20 released! Now officially a gradually typed language: Elixir type checks every single line of code, finding bugs and dead code, without developer overhead (no typing signatures) and extremely low false positives rate. Plus a faster compiler! Links and reports below.
Tjaco Oostdijk retweeted
Claude/Codex + Elixir + Phoenix + LiveView is such an insane superpower.
The entire stack, from low-level distributed systems modeling all the way up to the UI, is all built in one language & runtime that's easy to reason through.
Tjaco Oostdijk retweeted
Code BEAM Europe call for talks ends this week ⏳ This is a rare chance to speak in a philharmonic concert hall, so submit some proposals, take that beautiful stage, and you'll get to tell your grandchildren stories about it 😏️
sessionize.com/code-beam-eur…
Tjaco Oostdijk retweeted
Half the code (50k → 26k LOC), deleted a 666 MB Node.js SSR pool, killed the weekly OOM crashes, dropped every npm dep. one language top to bottom. less rope. Bonus: also swapped Fly Managed Postgres for Unmanaged on the way through. total bill dropped from $30+/mo to $13/mo
Tjaco Oostdijk retweeted
Code BEAM Europe 2026 is coming! 🚀
Want to secure the best possible ticket price? Join our waiting list today and be the first in line when Early Bird tickets officially launch! 🎟️
📅 The exact dates and the waitlist sign-up are available on our website.
📍 Haarlem, NL & Virtual
👉 Join the waitlist here: codebeameurope.com
#CodeBEAM #Erlang #Elixir #Gleam
Tjaco Oostdijk retweeted
I believe in the EEF! @TheErlef
I'm on the board so I get to see first-hand the amount of work and toil that goes into making the #ElixirLang, #Erlang & greater #BEAM ecosystem better.
What I also get to see, though, is how much we need your help. Relative to the revenue generated by companies that use Elixir, the EEF has a pittance.
Most of us know what's happening the OSS world and security right now. What you probably don't see is the massive amount of coordination and scrambling going on at every level to secure the open source ecosystem. While this may have been operating at a sustainable pace before, the advent of AI has fundamentally changed the game.
The EEF maintains a CNA, and actively coordinates and advises across the board on security issues. They are helping to make our languages more secure, and even hex.pm!
But the bad news here is that this is no longer sustainable. We need people who are generating revenue on the BEAM ecosystem to pitch in. We need a bigger team of people solving these problems because what we have is barely enough as is.
The real problem, however is that this is progressively getting worse by multiple orders of magnitude. CVEs coming in left front and center.
This is a tragedy of the commons. People are not helping foot the bill for our open source ecosystem. Before that used to mean "inconvenience", as you had to fork packages or version mismatches. But now? Now it means getting pwned.
Join me in becoming a member of the EEF, and please, if you run a company built on a BEAM language: DONATE.





















