The whole code base is a vibe coded rewrite, half a year after Bun was acquired by Anthropic.
I see lots of ground for that claim.
The whole code base is a vibe coded rewrite, half a year after Bun was acquired by Anthropic.
I see lots of ground for that claim.
I apologize, may I ask you, do you use Bun? If yes, you probably do monitor the development of this project (I do, it sounds reasonable to track your tools/deps), probably familiar with Jared's coding style, decision making process, architecture nuances, previous choices? Do you have any issues opened/closed in Bun's repo? Were you satisfied with contributors' reaction? Do you feel you can trust devteam behind Bun?
I get it if you're trying to defend your buddy, but at the end of the day it's on software to justify itself to me. Not for me (or parent poster) to justify their refusal.
Once bitten twice shy, y'know. Maybe the first bite wasn't even from bun. If bun can't take this on the chin and come back stronger, maybe bun wasn't a good choice to begin with. I'm sure a future version of bun with a rebuilt reputation will have an easy time getting re-adopted by most projects that needed to play it safe during the transition.
There is no evidence that it was "vibe" coded. It was ported to Rust by an expert engineer using an AI tool using solid SWE practices.
1 million lines of code in 7 days = ~6000 lines of code to be reviewed per hour, 24 hours per day.
or... they just trust that their ai got it right, which to most people is "vibe coding".
It was not ported by an engineer. It was transpiled by an LLM and no engineer has ever seen those 1mloc.
How can you claim following SWE best practices if couldn't realistically even have read the code?
1 million lines of code written and approved, in 9 days proves without reasonable doubt it was vibe coded.
In 7 days?
That's just agreeing with extra steps.
Those SWE practices were so solid that the rewrite was already rolled back!
[dead]