For the first time in 10+ years, the Erlang runtime is getting a new native data type

On the latest BEAM There, Done That, Francesco Cesarini and Allen Wyma sit down with Björn Gustavsson - the “B” in BEAM - for a deep dive into the history and evolution of Erlang/OTP.

Topics include:

• why records started as a “temporary hack”

• why maps never fully replaced them

• what finally made native records possible after nearly 30 years

• BEAM internals, compiler tradeoffs, runtime tagging, and VM evolution at scale

-record(state, {curiosity = infinite}).

If you enjoy language design, runtimes, distributed systems, or understanding how production VMs evolve over decades, this episode is packed with insights.

Some friendly feedback about the “Building Real-Time AI Agents with Kimutai Kiprotich” episode.

I think the guest missed some really important questions that I wish the hosts would have followed up on.

One in particular was about how to do context reloading after a process crash.

The guest responds by saying, “it’s already in a supervision tree and each agent has its own state. So if it fails, we’ll just restart that agent and it will continue doing so.”

However, there’s no answer to the most important part of this question which is how to reload context.

Does anyone have an answer to this? Super interesting question with important implications for anyone who wants to provide high-quality, long-running agents in an enterprise setting.

I would love to have like a timeline thing so I can jump to different parts of the video. I don’t really have time to watch an entire hour, so I’m more likely to not watch it at all even if there would be bits that interest me.