So the "Bun being a vibe coded rewrite from Zig to Rust" is a different story than I think it's being sold as, from everything I can see.

[cwebber@social.coop]

Note that this rewrite has a lot of resources at its disposal. The porting.md file has a ton of direction, more than historically an LLM can keep track of: https://github.com/oven-sh/bun/blob/46d3bc29f270fa881dd5730ef1549e88407701a5/docs/PORTING.md

But Anthropic acquired Bun, so I imagine this project has effectively as many tokens to use as it wants.

If this rewrite succeeds, this will effectively not only be a "fuck you Zig for not accepting my AIgen patches", it'll be a big headline and marketing story for Anthropic: look! Claude could rewrite Bun from Zig to Rust!

It's hard for me to read this then as anything but an experiment to see if Anthropic can get a big marketing boost in favor of vibecoding from.

[wordshaper@weatherishappening.network]

@cwebber ...wow. Read that thread on xcancel and there is some weapons-grade wishcasting going on. I'm assuming this dude thinks AI will also give him a pony and a lollipop when he asks too.

[cwebber@social.coop]

But this won't be an ordinary vibecoding story if it succeeds, but it might *look that way* from a marketing perspective. It has the lead maintainer giving a *ton* of guidance and perspective. It has the resources of Anthropic itself at its disposal. And it has the perfect story attached to it, so there's a lot to win if it succeeds, and little to lose if it doesn't, since the failure can just be ignored and they can move on.

[hellbeast@pleroma.envs.net]

@cwebber stories like these make me want to quit computing entirely, i'm tired of this, i'm tired of sharing spaces and hats with this capital machine

[wakame@tech.lgbt]

@cwebber

while(not_ported_correctly) {
  manually_add_guidelines();
}

[cwebber@social.coop]

@be Oops! Thx. Transposition!

[ridley@hachyderm.io]

@cwebber > I expect OSS to go the opposite direction: no human contribution allowed. Slop will be a nostalgic relic of 2025 & 2026.

Clearly someone whose professional opinions should be trusted. /s

[federicomena@mstdn.mx]

@cwebber I don't understand being the lead of a project, ostensibly understanding most of the code and its history, and slopping it up into an AI translation that you don't know at all. Yes, please turn my carefully handcrafted artifact into a pile of legacy code, at scale.

[ridley@hachyderm.io]

@cwebber Maybe I'll just save that comment for the next time I feel imposters' syndrome.

[dalias@hachyderm.io]

@cwebber LMAO at these Bun clowns. Props to Zig folks for shooting down their slop without even having to mention that it's slop.

[aburka@hachyderm.io]

@cwebber I agree, it actually has little to do with the Zig compiler's AI ban. Zig isn't saying "please don't write zig apps using AI"

[aburka@hachyderm.io]

@cwebber also holy crap that is an *extensive* porting guide

[algernon@come-from.mad-scientist.club]

@cwebber

What can we make of this?

Silicon Valley White Men need therapy, badly, because they're out of touch with reality.

[defuneste@fosstodon.org]

I do not know much but giving infinite money to some folks seems to cause issues..

[aburka@hachyderm.io]

@be @cwebber not clear to me that changing the implementation language to rust will help with that though

[liberty@mathstodon.xyz]

@aburka @be @cwebber Unfortunately Rust hasn't come out nearly as strongly against LLMs used in contributions

[aburka@hachyderm.io]

@liberty @be @cwebber true, but they're not exactly notorious for moving quickly on language changes

[datarama@hachyderm.io]

@be @cwebber The entirety of the software world by now feels like one massive, foul-smelling heap of high-yield embarrassment.

[vathpela@infosec.exchange]

@federicomena @cwebber Except the "at scale" part is a bit of an illusion. It's a one-off with resources almost no other project can hope to have in the near term.

[reiddragon@fedi.catto.garden]

@cwebber It's people like this for whom the saying "don't get high off your own supply" was coined