I hope they ship and use this. It’ll be a super interesting case study in a few years.
> Read this whole document before writing any code.
Hm does that actually work?
Edit: in a way that can be verified, and not the AI tool saying it did
I guess it's like Trump saying, "I'll take Greenland too..."
April 26th - Bun announces they used AI to fork Zig so they could make an optimization for a 4x improvement
April 27th - Zig contributor mlugg clarifies why the specific optimizations Bun did were ill advised and wouldn't have been accepted in Zig, regardless of AI use [1]
May 4 - Bun is looking into Rust as an alternative.
This, to me, seems like total whiplash. Has anyone at Bun made a statement on why they're making such dramatic changes? It seems like the lesson to internalize from mlugg is not "switch to Rust"
[1] https://lobste.rs/s/ifcyr1/contributor_poker_zig_s_ai_ban#c_...
Interesting. When I thought of Zig, I thought of Bun. In my mind it was the flagship application for that language. Is there another? I wonder how the Zig team feels about this. To me it seems like Rust has definitively won now.
>*No `tokio`, `rayon`, `hyper`, `async-trait`, `futures`.* No `std::fs`,
I'm not a rust dev but even I kind of notice that tokio is kind of shunned in most projects. Why is that? Is it just bad or what?
Here we go again ...
Company A buys company B. A's management decrees the henceforth B's aqcuihired team must comply with company A's standards.
Second system effect kicks in. Bugs multiply.
Half of original company B devs leave.
I'm investigating whether future projects should revert to using Deno.
instead of writing it once in C++
what a win
it will make it more portable.
[dead]
[dead]
[dead]
People are asking why they would switch from zig to rust. I wonder the opposite: why would anyone would use zig over rust?
Makes sense on merit. There really isn’t room for Zig when Rust exists, is more ergonomic, and also safe.
I fully support this decision
"Claude, migrate bun to Rust, make no mistakes"