Bun has been converted to rust. Now what?
bytecode.news
Bun has been converted to rust. Now what?
1–10 of 113 posts
Re: Bun has been converted to rust. Now what?
#2Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?
Re: Bun has been converted to rust. Now what?
#3Deno was already implemented in Rust, and not done by vibe-coding.
Would you trust a fully vibe-coded runtime? Not some features, not some fixes, but a full translation from one language to another.
Re: Bun has been converted to rust. Now what?
#4Deno was already implemented in Rust, and not done by vibe-coding. Would you trust a fully vibe-coded runtime? Not some features, not some fixes, but a full translation from one language to another.
yes
Re: Bun has been converted to rust. Now what?
#5Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?
For one, you now know exactly where the memory unsafe code is, rather than a cloud of suspicion hanging over every line of the codebase.
Re: Bun has been converted to rust. Now what?
#6Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?
Were "passing tests" also generated by the same LLM?
This is much different from how Ladybird team handled a rewrite: https://news.ycombinator.com/item?id=47120899
Re: Bun has been converted to rust. Now what?
#7Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?
Preparation, but this is prep for a scale that the maintainer is going to solve by more LLM-assisted coding, probably.
Unsafe blocks are not inherently bad, but it's good that these are explicit unsafe blocks. It's like saying TODO comments are bad. It depends.
Re: Bun has been converted to rust. Now what?
#8Couple of notes here:
- This is blatantly irresponsible, and killed any credibility this project has
- Comparing unsafe counts to UV makes no sense here.
- There is already a strong, safe runtime that's not vibe coded, called Deno, that more people need to check out.
- I am skeptical why Bun was even an acquisition target in the first place, other than pulling stunts like this.
Re: Bun has been converted to rust. Now what?
#9Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?
- A substantially simpler, more-contained build process
- A base from which to build upon by removing unsafe blocks
Re: Bun has been converted to rust. Now what?
#10The irony of a post about a port primarily written by Claude having been primarily written by Claude on a website primarily designed by Claude. Come on.