4 ms·

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.

by bhaak 4mo ago

doug_durham 4mo ago
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.
- 1attice 4mo ago
  That's just agreeing with extra steps.
- vor_ 4mo ago
  In 7 days?
- b40d-48b2-979e 4mo ago
  Those SWE practices were so solid that the rewrite was already rolled back!
- cheesefck 4mo ago
  the speed of the rewrite and various analyses of the resultant codebase provide ample evidence that it was vibe coded and solid SWE practices were ignored nobody understands the Bun Rust codebase. I wouldn't risk my business on code understood by no person. who is responsible? who will take accountability? nobody. into the trash with it.
- oytis 4mo ago
  How can you claim following SWE best practices if couldn't realistically even have read the code?
  - shimman 4mo ago
    "Please follow best practices." You're telling me that isn't good enough? You might need to head off to the VC reeducation camps.
  - doug_durham 4mo ago
    So transcoding doesn't work unless every line of code is read? That's not how transcoding is done in practice.
    - bhaak 4mo ago
      But the code that does the transcoding has been read. Somebody needs to have read deterministic code to even have a chance of noticing something being wrong. This has not happened here.
- egorfine 4mo ago
  It was not ported by an engineer. It was transpiled by an LLM and no engineer has ever seen those 1mloc.
- 12345hn6789 4mo ago
  1 million lines of code written and approved, in 9 days proves without reasonable doubt it was vibe coded.
- john_strinlai 4mo ago
  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".
leobuskin 4mo ago
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?
- dogleash 4mo ago
  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.

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.

by bhaak 4mo ago

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.

doug_durham 4mo ago

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.

1attice 4mo ago
That's just agreeing with extra steps.
vor_ 4mo ago
In 7 days?
b40d-48b2-979e 4mo ago
Those SWE practices were so solid that the rewrite was already rolled back!
cheesefck 4mo ago
the speed of the rewrite and various analyses of the resultant codebase provide ample evidence that it was vibe coded and solid SWE practices were ignored nobody understands the Bun Rust codebase. I wouldn't risk my business on code understood by no person. who is responsible? who will take accountability? nobody. into the trash with it.
oytis 4mo ago
How can you claim following SWE best practices if couldn't realistically even have read the code?
- shimman 4mo ago
  "Please follow best practices." You're telling me that isn't good enough? You might need to head off to the VC reeducation camps.
- doug_durham 4mo ago
  So transcoding doesn't work unless every line of code is read? That's not how transcoding is done in practice.
  - bhaak 4mo ago
    But the code that does the transcoding has been read. Somebody needs to have read deterministic code to even have a chance of noticing something being wrong. This has not happened here.
egorfine 4mo ago
It was not ported by an engineer. It was transpiled by an LLM and no engineer has ever seen those 1mloc.
12345hn6789 4mo ago
1 million lines of code written and approved, in 9 days proves without reasonable doubt it was vibe coded.
john_strinlai 4mo ago
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".

leobuskin 4mo ago

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?

dogleash 4mo ago
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.