Earlier quoted context omitted.
Just because the machines can generate code that quickly doesn't mean that human thought has changed to moving faster. Everyone's had a problem they were working on, and the solution doesn't come sitting at the desk staring at the code, but three days later in the shower, eureka! hits. Just because machines are writing code hasn't changed the underlying human thought speed substrate. That's why people see nine days a…
Human speed thought doesn't matter here because it's not human reviewed. The code was generated. It exists and it (now) works to the extent they're satisfied with going through with a canary release. Going on about about '9 days' is working with a mental model that simply does not apply here. That is my point. If you think there should be human review or that there should have been a lot more human collaboration, tha…
Rewrite Bun in Rust has been merged
561–570 of 822 posts
Re: Rewrite Bun in Rust has been merged
#562I will move the handful of my projects that use Bun to something else. I don't trust governance that permits this kind of reckless change.
It doesn't need to be rewritten because it was written well in the first place.
Re: Rewrite Bun in Rust has been merged
#563If this goes wrong even in the slightest , the ridicule about a drug dealer getting high on their own supply will be neverending and grim.
not enough people are emotionally prepared for if it’s not going wrong even in the slightest
Re: Rewrite Bun in Rust has been merged
#564Re: Rewrite Bun in Rust has been merged
#565Earlier quoted context omitted.
The maddening thing is that there's a right way to do this if you have the patience and professionalism to do so. It requires building a bit of scaffolding (feature flags, cross-language calling support, harnesses for shadow testing, etc.), then you ship-of-theseus the codebase incrementally . This is not even incompatible with LLM-assistance, plus it breaks the thing up into smaller, reviewable changes that don't br…
There is never a right way, only trade offs. The thing about being a Monday morning quarterback is that you can always claim you would have used even more caution and process.
Re: Rewrite Bun in Rust has been merged
#566By reading this thread I've learned that, apparently, you are not allowed to rewrite a large piece of software backed by a large test suite in another language within two weeks otherwise you are a witch and need to be burned on a stake. You are also not allowed to move from the PoC phase to lets-do-it phase within a couple of days without being called names. Why are we concerned with speed all of a sudden? Are we in…
I can't ignore how much this sounds like Stockton Rush. > "Apparently if you build a submersible with carbon fiber you are a witch and need to be burned on a stake. But look we're making reliable trips down to the Titanic with no problems." Realistically, this is a forum of experienced engineers watching a company make some extremely questionable but very flashy engineering decisions. There's going to be a lot of peo…
Re: Rewrite Bun in Rust has been merged
#567Earlier quoted context omitted.
It’s still 400k more lines
Dunno where you got that number from but it's half that. Tokei says: =============================================================================== Language Files Lines Code Comments Blanks =============================================================================== Zig 1298 711112 577946 57772 75394 Rust 1443 931232 737485 114373 79374 So it's 28% more lines of code (not comments/blanks).
Re: Rewrite Bun in Rust has been merged
#568I'm curious where this leaves Zig. Bun was the most prominent and biggest project using it. What's left?
Re: Rewrite Bun in Rust has been merged
#569I'm curious where this leaves Zig. Bun was the most prominent and biggest project using it. What's left?
Re: Rewrite Bun in Rust has been merged
#570I just skimmed through the porting guide and based on the number of unsafe blocks, this looks like a fairly straight-forward mechanical translation. If that is the case, why didn't they just "vibe-code" a Zig->Rust translator and a small Rust/TS/JS/whatever script to orchestrate things. You don't even need pretty printing support because rustfmt exists. You'll save on a bunch of tokens, probably a lot of time/enegy,…