Join Nostr
2026-09-09 13:00:17 UTC

:seven: on Nostr: Erlang is wonderful and I love it but I worry I know it too well now. Something ...

Erlang is wonderful and I love it but I worry I know it too well now. Something Erlang can’t promise, something that has existed as a regretful constraint on the system basically since JAM, is that the scheduler cannot promise deterministic spawn-then-trap-first-thing behaviour across multiple worker threads.

It’s not perfect but I can promise that, at a very slight performance overhead that I kinda have to spend anyway: I need to run a single slice of the process’ budget to make it provably alive for determinism. But everything is still faster than when I used the naive scheduler and process model, so performance everywhere else is doing enough heavy lifting to compensate.