The Zig Evangelism Task Force has supplanted Rust as the premier hypebeast. And they'll be supplanted by the NEXT BIG THING.

I'm saying you have to be as meticulous as a borrow checker. Not as strict, of course, but you have to analyze each pointer, how and when it's used, and then cross-reference with the documented lifetime.

Just like thread safety existed before Rust made it explicit. Now you don't need to investigate if data is thread safe if it's `Send + Sync`.

This is a job humans suck at and compilers excel at. With some caveats. There will be edge cases that will need to be manually proven.

> TBH in hindsight it seems that the Bun acquisition was also for the PR stunt they just did with the Rust porting.

The events went roughly like this:

- Anthropic used Bun. So they acquired it.

- Bun made some LLM derived patches for Zig. They were rejected due to Zig no-LLM stance.

- Bun couldn't get patches in, so they switched to Rust.

Was it a PR stunt, an attempt to pressure Zig maintainers into changing AI stance, or just doing the fastest thing possible? It's difficult to tell. I'm inclined to believe the last option.

As easy as it is to blame Bun for a PR stunt, it's also possible that you can't really associate with someone who rallies against your employer/owner.

Not really. LLMs are a tool, and they do possess some interesting properties, but they are, in essence, a very surprising auto-complete.

No, what sucks is the AI companies marketing them as if they are The Holy Grail. And people are assuming that somehow LLM -> AGI -> ASI, even though there isn't really a causal link to be had, and acting like it's The Singularity.

I don't blame autocomplete for fucking up RAM, labor and god knows what else. I blame the idiots (at OpenAI and Anthropic) buying all RAM stocks and pretending this shit is any way good for anyone.

Honestly, I think it would have been better if he had done the smart thing and ignored the noise around Bun's Zig -> Rust, and focused on code.

If he was willing to ride the coattails of Zig being hyped by Bun, then he should have taken the hit when Zig and Bun parted ways.

Hell, if he is that happy that they are leaving, he shouldn't have written that he is happy. Just smile and wave...

So now Jarred wrote a very matter-of-fact post about migrating Bun to Rust, and Andrew Kelley wrote a ranty blog about Jarred sucking at Zig, and being glad he's gone.

Sixty years ago the model was you go to an arcade cabinet, and you get charged every time you died (Credit: https://www.penny-arcade.com/comic/2026/07/03/returnal-3).

Ideally, they want cabinet in every home, you pay electricity for it, you buy overpriced Bluey skins, you buy your lives, you buy ads, and pay them every second for the pleasure, while not owning even the cabinet.

It doesn't take much for one memory inefficient dep to drag down the entire app.

Yes, this is the difference between a BDFL. A single person can make a decision faster, than a group of people. And consensus often leaves most people a bit miffed.

Again, the issue starts when the dictator grows mad and starts making decisions that make every contributor uncomfortable.

> To my horror, many software projects were accepting LLM-generated code. I had thought LLMs were unpopular among developers.

Why would a really stochastic auto-complete and analyzer be disliked by developers? LLMs are a useful tool, sometimes, but they aren't the levels of hype that current frontier labs need to justify their costs.

> But Memory Safety!

I'd be genuinely flabbergasted if Zig ends up as safe as Rust without any overhead. So, no, adding Fil-C doesn't count. We have memory safety with overhead. We call it Java/C#/JavaScript/Go/.

A good WYSIWYG editor will run circles around the fastest text editor. Even if WYSIWYG is a bit slower to open.

It would be preferable for software to be more focused and faster over time, but that doesn't attract people to it.

Not really. If anything I'm pretty sure Fred would compare it to Ada:

    > Nevertheless, Ada will not prove to be the silver bullet that slays the software productivity monster, It is, after all, just another high-level language, and the biggest payoff from such languages came from the first transition, up from the accidental complexities of the machine into the more abstract statement of step-by-step solutions.

From what I last heard about crypto miners, the price of mining is not enough to justify price of rig + electricity, so they are quietly switching to AI.

Wonder how long the second scam will last.

Edit: Someone on Reddit compiled a list of various fuckups. https://www.reddit.com/r/browsers/comments/1j1pq7b/list_of_b...

And the Rust wasn't the root cause but corrupt configs were being erroneusly duplicated.

Arguably less bad than silently corrupting your data and forcing you to do CAPTCHA everywhere.

Which is what the parallel Perl(?) component was doing at the time.

Rust solution gave a clear signal something was wrong, the other solution was slowly annoying everyone and pushing them away.

Did you check if I name my project 朽木?