Comment by gorjusborg
8 hours ago
Very smart. You can't lose all your customers for vibe-coding a migration to Rust if you are already written in Rust ;)
8 hours ago
Very smart. You can't lose all your customers for vibe-coding a migration to Rust if you are already written in Rust ;)
They'll get bought out by OpenAI and convert the project to Zig
huh, is OpenAI embracing Zig specifically? TIL
It’s a joke about how Anthropic bought bun and then rewrote bun from zig to rust with a giant one week vibe code. The joke hinges on the fact that this would be the opposite (OpenAI, nub, rust to zig)
1 reply →
Yea, not sure what “written in rust” adds to this. I would have thought that you could get the same functionality with a few shell scripts and a package.json.
I assume speed.
But also, I know “rewrite in Rust” is a meme but if you’re doing something new, why not? I can’t see a good argument that a pile of shell scripts would be a superior way to organise things.
There's a difference between running your app on a vibe coded runtime or just local DX tools though.
This project is already highly vibe-coded. Claude is the second contributor of the repo.
It also helps if you're already vibe-coded and don't have customers to begin with
Bun had customers?