I don't know any bad stories about ai-translated apps. Partially because it's a relatively new trend, but also because a big amount of usual vibe code fail modes are not applicable here.
2. Even if somehow you did make bug-free software with tests alone, even if the Rust port is perfect today owing to the years of careful human work that went into building tests as a framework to guide the AI... the future can only be downhill from here. Nobody has a mental model of the new 1m loc codebase that's never read by a human, so Bun's future is committed to 100% vibecoding. Maybe the carefully planned tests minimized the worst case scenario, but the future tests will be written by Claude too.
If, and this is a big if, it turns out that there are no major problems and Bun is better off in a year from today than it is now... then somebody can just fire up Claude and fork yt-dlp to support Bun anyways and their decision doesn't matter. In any other scenario than human code becoming completely obsolete, they are simply saving themselves a headache by getting rid of a troublesome dependency.
There's something really satisfying about a go binary with minimal dependencies running in a busybox docker container.
I'm quite liking how good Claude Code Opus is at Rust + sqlx (raw SQL with type safety) + actix-web.
It is impossible to review the entire rewritten codebase. There are just too many lines of code, 1 million lines to be exact [1].
Deno and Bun have decent Node compatibility, so couldn't Node APIs be used as the generic runtime interface?
--js-runtimes [deno|node|bun|quickjs]
hootz•43m ago
LoganDark•20m ago
(Hilarious in the way that's terribly sad, of course.)
abnercoimbre•16m ago
em-bee•8m ago
vosper•15m ago
happytoexplain•9m ago
tedivm•7m ago
colordrops•9m ago
gpm•6m ago
hootz•5m ago