ThinkingElixir

Helping teams and individuals adopt Elixir and thrive. Elixir courses and podcast.

[Elixir by Software Mansion @swmansionElixir]

Voyager 0.2.0 has landed! 🛰️

Your BEAM inspector just got deeper:
🗄️ Browse and search ETS tables
⚙️ Process list and detailed process view
🤖 Full AI support for both via MCP

Take a look 👇

[ThinkingElixir @ThinkingElixir]

@georgeguimaraes Nice troll. 👹

[Leandro Pereira @leandrocesquini]

Lumis now lets you choose which languages to load in your package. Need only Elixir and Rust? That's only 2mb vs ~130mb of the full bundle. Just add:

{:lumis_wasm_elixir, "~> 0.26"}

That also applies to MDEx and MDEx Native. See https://t.co/HMI2Oho8zH

https://t.co/iopvqBHnQl

[ElixirConf @ElixirConf]

🔥 4,000 views over the weekend! @chris_mccord with "What Comes Next" keynote from ElixirConf US 2026. Watch it here: https://t.co/j6Ktk3T47U
Craving more videos? Grab the video pass: https://t.co/ZR47pCHBJf
Curious what's next? Code BEAM Europe, 21-22 Oct, Haarlem NL + online

[Superman @thesupermannx]

China published the most uncomfortable paper on vibe coding.

ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds.

The findings are brutal.

The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning.

They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself.

Two major predictors emerged.

Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds.

But that wasn't even the main takeaway.

Computer science achievement was a massive, dominant predictor of success.

Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed.

In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone.

Why? Because vibe coding isn't about writing code. It’s about debugging logic.

When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works.

They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe.

You can prompt your way past syntax.

You cannot prompt your way past a fundamental lack of engineering intuition.

The hype told us that learning to code is dead because language is all you need.

The data just proved the opposite.

To truly master the vibe, you still need to understand how the machine thinks.

[José Valim @josevalim]

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.

[Erlang Ecosystem Foundation @TheErlef]

Erlang/OTP security release: 29.0.4, 28.5.0.4 & 27.3.4.15 fix 8 vulnerabilities, including TLS/DTLS auth bypass, BEAM VM memory corruption, and a path traversal bug.

Learn more: https://t.co/1xKDkw82AF

[José Valim @josevalim]

In a podcast, @_lopopolo also said that when they built the SPEC for Symphony, they had to rebuild the project from the SPEC multiple times and refine the SPEC to make sure it built the same project consistently.

Therefore (my words now), your spec is not a clear and unambiguous specification of your codebase, unless you are constantly rebuilding and refining the spec. And nobody is doing that.

Plus remember that different models and versions interpret instructions differently, so the spec you wrote or refined for Opus 4.6 may not generate the same thing on Opus 5 or ChatGPT Sol.

And that’s one of at least a dozen reasons why comparing LLMs to compilers is non-sense.

[Hex @hexpm]

Hex v2.5 adds three layers of supply chain defense: security advisories in your terminal on mix deps.get, a release-age cooldown that withholds new versions until they’ve aged, and organization policies for filtered dependency fetching.

https://t.co/VthyhsG26V

[Elixir by Software Mansion @swmansionElixir]

We’ve just released LiveStash v1.0.0 for Phoenix LiveView! 🎉

What’s new?
⚡ Mnesia adapter with cluster state replication and split-brain auto-heal
🔒 Explicit security configuration for browser memory storage
🛡️ Stability & performance improvements (more on that in 🧵)

[Bart Blast @Bart_Blast]

Hey Elixir friends! :) A real event system comes to Hologram - v0.10 is out! You can now handle keyboard, scroll, resize, click-outside and scroll-edge events, bind handlers to the window and document, and debounce or throttle the noisy ones, all in your templates with compile-time checks. To show it off, I rebuilt Space Invaders in pure Elixir, running in the browser with no game engine. Plus a new server-side middleware layer, and comprehensions and try/rescue now run the same on the client as on the server. More here: https://t.co/epwkW5Gt7s

[ThinkingElixir @ThinkingElixir]

@hugobarauna @josevalim Love it! This is how I work too. It makes the most sense to me.

[ThinkingElixir @ThinkingElixir]

@Straffern @germsvel @brainlid @bernheisel I'm glad you were able to start working in Elixir! That's great to hear. That's what it was all about for me. Getting people excited about Elixir and providing a community service. Best of luck to you going forward!

[ThinkingElixir @ThinkingElixir]

The final episode! After 6 years, we close with news on LiveView 1.2 colocated CSS, Earmark’s retirement, Sagents v0.8.0, #Postgres 19, @SpaceX buying @cursor_ai for $60B, and what’s next for David and Mark! @ElixirLang #ElixirLang https://t.co/gwciLQR6eR

[ThinkingElixir @ThinkingElixir]

Elixir v1.20 is officially a gradually typed language, HexDocs moves to per-package subdomains, the #Miasma worm hits 73 @Microsoft @Github repos, and more! @ElixirLang #ElixirLang #security https://t.co/bj3NbM9Lzz

[Phoenix Framework @elixirphoenix]

Phoenix LiveView 1.2 is released with colocated css and more! Check the announcement for details!
https://t.co/MpGC3QzXji

[ThinkingElixir @ThinkingElixir]

Ecto 3.14 ships UUIDv7 support, Oban Pro adds human-approval workflow steps, Hologram v0.9 brings pure-Elixir realtime push, @Dashbit shares Tidewave's Git integration design, and the NSA drops new Zero Trust guideline, and more! @ElixirLang #ElixirLang https://t.co/YLNl0rIbdm

[Bart Blast @Bart_Blast]

If you write Elixir, you know the moment the fun stops. It's when you leave it for the frontend.

For me the low point was an afternoon lost to a bug that turned out to be an object quietly mutating three files away - the kind of thing Elixir just doesn't let happen.

And it's not just that one bug. No real pattern matching. Mutable state everywhere. An equals sign you can't fully trust. The pile of footguns we've all just learned to step around.

I don't think that's fine. I think we got used to it.

So Hologram lets you write the whole app in Elixir, frontend and all. Honestly, the real reason is simpler than all that: I just want to write Elixir all day. It's a stupid amount of work to get there. I regret nothing :)

[ThinkingElixir @ThinkingElixir]

@rr_cook Yes! But at some point I’ll transfer it to another podcasting home that doesn’t cost me to maintain the back catalogue.

[ThinkingElixir @ThinkingElixir]

It’s true! After 6 years of weekly episodes, the Thinking Elixir Podcast will be ending on June 23rd. Three episodes left. It’s been an incredible run and I’m grateful for every listener who came along for the journey. #podcast #MyElixirStatus #ElixirLang

[José Valim @josevalim]

https://t.co/T4UYnB1X5c