Rewrite Bun in Rust has been merged
201–210 of 822 posts
Re: Rewrite Bun in Rust has been merged
#202PR so thick, the page failed to load the first time I opened it, and the comments still continue to fail to load. Absolutely hilarious. Though that may be just GitHub having a normal one, hard to tell these days. 1 009 257 lines added 4024 lines removed 6755 commits 2188 files touched I haven't the slightest clue how anyone would even remotely hope to review this. I guess by just using even more AI? Or maybe by throw…
Re: Rewrite Bun in Rust has been merged
#203Earlier quoted context omitted.
You, nine days ago[0]: > I work on Bun and this is my branch > This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely. Maybe... it wasn't such an overreaction? [0]: https://news.ycombinator.com/item?id=48019226
You're not alone in voicing this, another (now dead) comment did it earlier too with a bit more of an emotional response ( https://news.ycombinator.com/item?id=48134229 ). Still, do you folks never do something to see how you feel about something, then chose to go one way or another? I'm not sure why it's so hard to see that it was an overreaction at the time, because it was an experiment, then at one point it stoppe…
Re: Rewrite Bun in Rust has been merged
#204I'm actually excited for somebody trying experimenting with automated translation, but I'm afraid this will be lots of backwards compatibility issues. I started looking at the commits, and it's basically solving the ,,tests not pass'' problem by changing the tests themselves. The real work of making it working on programs that are already deployed will be just starting now. The only silver lining I see is that the se…
I'm convinced the future of writing code is heavily LLM assisted
[0] https://tsz.dev
Re: Rewrite Bun in Rust has been merged
#205The follow-up PR removing the zig source files being auto-tagged by bun's own CI as "ai slop" is so funny https://github.com/oven-sh/bun/pull/30680
That was me - not CI marking as slop. It kept around 60 .zig files around that should’ve been moved to .rs files.
That's wild, how are people going so crazy over a rewrite.
Re: Rewrite Bun in Rust has been merged
#206Re: Rewrite Bun in Rust has been merged
#207If LLMs can achieve this level of task in 9 days, why do we even need Bun in the first place? Shouldn't we just write our apps in Rust and not even deal with JS?
Re: Rewrite Bun in Rust has been merged
#208Earlier quoted context omitted.
Well it was 9 days ago, at the time they were not confident, but maybe the results were insanely good.
no matter how good the results are, this kind of rewrites deserves an experimental build to be battle tested by bleeding edge users. It takes a lot of rigorous testing automated and manual and by community before such changes are cosnidered permanent. One does not simply YOLO a full langugae rewrite without user feedback. it is insane.
The Zig version has not been removed and this only exists got canary builds. No rust binaries are being distributed as stable.
Re: Rewrite Bun in Rust has been merged
#209Earlier quoted context omitted.
no matter how good the results are, this kind of rewrites deserves an experimental build to be battle tested by bleeding edge users. It takes a lot of rigorous testing automated and manual and by community before such changes are cosnidered permanent. One does not simply YOLO a full langugae rewrite without user feedback. it is insane.
You should really read TFA because... that's exactly what they're doing? The Zig version has not been removed and this only exists got canary builds. No rust binaries are being distributed as stable.
Re: Rewrite Bun in Rust has been merged
#210Earlier quoted context omitted.
That's picking up all the "bunsafety" references in there :P
When I read what you wrote, I was like "of course, duh, I'm stupid" but running `ag "unsafe" src | grep -i "bunsafety"` it doesn't seem to be the case actually, I see zero bunsafety mentions from it. However, `ag unsafe` does over-count anyways, just in a different way, matching stuff like SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION and _unsafe_ptr_do_not_use and others. Better command with same previous commit, `ag -w…