An actual quote I am getting from Discord this week.
> Nix evaluation is catastrophically slow and i don't think it belongs in my builds
> ...
> i have very limited confidence in the ability of nix to evolve (both in technical and human factors). i am more optimistic about ideas like making the stuff running inside kinda agnostic to where it came from
From an actual experienced engineer on the ground managing a codebase with Nix.
This is why DHH is so freaking annoying.. not only does he not read what his bot writes . He also doesn’t read how his bot writes or asks the bot how it got to the solution. No interest in intellect or engagement . Bot would’ve told him asm is not load-bearing.
Looks like the gains were not from dropping down to asm
And rather just better design: DOD (SoA), only re-painting what was changed, writev to reduce syscalls, etc
All of which you could in Rust without asm!
Why shows to me that he’s just a bad prompter. A good AI user uses AI to learn so that next time you can prompt even better. Sure you don’t have to read the code. But you must absolutely read and write the prompts. And extract the context and understanding how things work
Like. The PR description *literally* says that asm is not why it’s fast. A good dev would then try to learn lessons from that and improve rust prompts so that next time they take into account data layout.
This was built in collaboration with us at @mercury after me complaining over and over again that outages due to space leaks in Haskell are a PITA to the respond to. No more!
Well-Typed are happy to announce Eventlog Live, which streams real-time telemetry from any Haskell application to any observability platform that supports the OpenTelemetry protocol! well-typed.com/blog/2026/09/…