7 ms·

absolutely, and `its development seems to have taken a turn towards being fully vibe-coded` ungrounded claim confirms the hysteria, I'm afraid

cizezsy 4mo ago
What are you afraid of?
- nish__ 4mo ago
  A codebase that no human understands.
- leobuskin 4mo ago
  I'm afraid "we" tackle (agressively) the wrong problem, also making it's tough for the maintainers, who did nothing wrong (I have a lot of sympathy towards Bun's developers, they got a lot of ugly feedback within the last month). I don't think AI-written code is the problem at all. Human signs off the changeset the same way as it happened before. I don't care if Rust rewrite did happen using pipeline/harness and LLMs, if the maintainer takes responsibility, and in projects like Bun it happens "by default", I think.
  - desecratedbody 4mo ago
    [dead]
  - cizezsy 4mo ago
    I agree with you that AI-written code should not be a problem and tons of open-source projects have AI-written code right now. But do you really believe the way Bun rewrites and merges its code to master is the same as before? The change in rhetoric (from "don't overreact, it's just an experiment" to "merge it anyway"), the never-arrived blog post promised to explain the decision are concerning to me. I really appreciate the maintainers' effort towards this awesome project. However, I think it is fair to be a little bit less confident with the current state of Bun.
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.

cizezsy 4mo ago

What are you afraid of?

nish__ 4mo ago
A codebase that no human understands.
leobuskin 4mo ago
I'm afraid "we" tackle (agressively) the wrong problem, also making it's tough for the maintainers, who did nothing wrong (I have a lot of sympathy towards Bun's developers, they got a lot of ugly feedback within the last month). I don't think AI-written code is the problem at all. Human signs off the changeset the same way as it happened before. I don't care if Rust rewrite did happen using pipeline/harness and LLMs, if the maintainer takes responsibility, and in projects like Bun it happens "by default", I think.
- desecratedbody 4mo ago
  [dead]
- cizezsy 4mo ago
  I agree with you that AI-written code should not be a problem and tons of open-source projects have AI-written code right now. But do you really believe the way Bun rewrites and merges its code to master is the same as before? The change in rhetoric (from "don't overreact, it's just an experiment" to "merge it anyway"), the never-arrived blog post promised to explain the decision are concerning to me. I really appreciate the maintainers' effort towards this awesome project. However, I think it is fair to be a little bit less confident with the current state of Bun.

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.