Apple Events these days as a European.
"Oh interesting" - Not available in EU and China
"Ah that's cool" - Not available in EU and China
"Wow I want to try that" - Not available in EU and China
#AppleEvent
Was reflecting earlier today on why we chose @elixirlang for @tuistdev’s server. Decided to share the reasons that have really stood out in practice:
1. Hot reloading. I can change a module and the app picks it up right away. This has been huge for staying in flow and iterating fast. Hard to imagine going back.
2. The Erlang VM (BEAM). In both dev and production you can see exactly what’s going on with processes, memory, and CPU usage. Super granular stuff. And now that we have coding agents, being able to tap into that runtime info feels even more valuable.
3. Phoenix LiveView. Building interactive UIs where state updates feel natural is just beautiful. No constant fighting with sync issues. And the best part? Testing it doesn’t force you to spin up a headless browser.
4. Concurrency. The model is so good you almost forget you’re dealing with concurrent code. The building blocks are thoughtful and battle-tested. Everything just works without the usual headaches.
5. Ecosystem. Pretty much everything we needed was already there: auth, observability, database stuff, you name it. That alone saved us a lot of time and boilerplate.
Overall I think Elixir is one of the strongest choices right now for building solid backend apps. The low-level runtime power combined with how well it plays with modern coding tools just feels like a really good fit.