If this goes wrong even in the slightest , the ridicule about a drug dealer getting high on their own supply will be neverending and grim.
Wasn't looking at leaked Claude Code source already enough for the ridicule?
Rewrite Bun in Rust has been merged
231–240 of 822 posts
Re: Rewrite Bun in Rust has been merged
#2329 days to review +1million LOC in Rust is enough? wow..
Re: Rewrite Bun in Rust has been merged
#233So the geniuses in the datacenter prefer to rewrite the full codebase in another language instead of maintaining and improving its own fork or contributing to make the current language better. Impressive to rewrite 1MLOC in a week yes, but this is more of a job of a million monkey programmers crammed in a datacenter than a bunch geniuses. And I would know, since I'm a monkey programmer who is in danger now... Or mayb…
> Or maybe the Zig team is in a greater danger, since their brains hold the genius juice the clankers are missing and they should have it by 2027
Imagine you want to monopolize programming by pushing LLM as an obligatory middle-men. Then people who can program without LLMs are direct threat to your business plan. It's time for us to start hiding. I'm cosidering adding `co-authored by Claude Code` to my hand-written commits and running Claude in useless loops to mock API usage.
Re: Rewrite Bun in Rust has been merged
#234Re: Rewrite Bun in Rust has been merged
#235Earlier quoted context omitted.
Yes sure it's ok to change your mind. But don't you think the people Jarred accused of "overreacting" in retrospect didn't?
No, what we knew then is still what was known then. Today is different, and seemingly they've committed to the rewrite, so now it makes sense that people have strong feelings about it, as it's no longer just an experiment.
Maybe the people who "were overreacting" just happened to have more foresight than you and me? Perhaps they saw where this was heading, and that led to their "overreaction"?
Re: Rewrite Bun in Rust has been merged
#236Wondering what they will do when rust rejects a pr from them.
I guess they vibe-rewrite to C, relying on CCC compiler. Agent loop will be modifying both the project and the compiler until the ends meet.
Re: Rewrite Bun in Rust has been merged
#237Honest question, how many of the leaks and crashes can be attributed to zig the language vs possibly (maybe, we don't know) a loosey-goosey, slot machine approach to development heavily reliant on AI? Will the inherent leaks and crashes be fixed, purely by dint of porting to Rust?
Re: Rewrite Bun in Rust has been merged
#238Earlier quoted context omitted.
not enough people are emotionally prepared for if it’s not going wrong even in the slightest
It's going to work for the most part. Most people know that. It's a file by file, mostly function by function, conversion from one low level language to another with a very large test suite (with lots of Rust unsafe to work around differences). I've done that for C tools and it's fine, with some obscure edge cases here and there. The challenges are going to be making the new, very ugly, alien codebase idiomatic Rust…
Just to clarify, you did this for C tools using LLMs or using deterministic conversion tools?
Re: Rewrite Bun in Rust has been merged
#239Turns out "its just an experiment, you all are overreacting" was just a lie to damp criticism. https://news.ycombinator.com/item?id=48019226
The experiment might have turned out well, or the author might have spent enough time to bring it to a place they was comfortable. Frustration moves mountains, I don't think this rewrite was done lightly.
The rewrite was obviously done lightly.
Re: Rewrite Bun in Rust has been merged
#240Earlier quoted context omitted.
"We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely."
People conflate “high chance of X” with “X will happen” all the time. See elections, for example.
The phrasing strongly implies that they are taking the migration seriously and carefully. Merging straight to canary after 9 days is insane.