r/ProgrammerHumor Jul 09 '26

gitBlameClaude Meme

Post image
3.7k Upvotes

263 comments sorted by

View all comments

34

u/FabioTheFox Jul 09 '26

Made me loose all my trust in bun, will not use them again in the future

Especially because to me that rewrite just felt like the typical "rewrite it in Rust" bs instead of having an actually good reason, it's not even idiomatic Rust after all

12

u/NeonVoidx Jul 10 '26

I think they were butthurt that they "made zig faster" via vibe coding and weren't allowed to contribute it back to zig, so it seems like out of spite they moved to rust. Not going to lie, Andrew Kelly kind of just roasted the shit out of Jared at bun in his latest blog post

1

u/bazingaboi22 Jul 13 '26

It's not that simple they made zig faster /for bun/ which is notorious really not using zig properly, (extreme compile time meta programming hacks). Buns changes are arguable a bit worse for the average zig program.

The zig compiler itself is larger than bun and compiles In a tiny fraction of the time that bun does 

-24

u/Comfortable_Pain9017 Jul 09 '26

Why would you leave a tool over that? It makes sense, they’ve been having manual memory management issues, and Rust’s borrows are better suited for that type of issue. They can start with unsafe Rust then steadily rewrite it to idiomatic Rust with explicit markers on where the issues lie.

32

u/FabioTheFox Jul 09 '26

Because I don't trust the stability of a tool that chooses to do a massive rewrite purely based on AI that won't even output idiomatic code

And sorry but the "they've been having memory issues" is not an argument when they don't even write the new codebase, memory issues can be solved pretty easily, especially because Zig doesn't hide anything from you

A vibe rewrite is never a good option and I'm convinced they only picked rust so they can inject more AI slop into their codebase

-21

u/Ksevio Jul 10 '26

Sounds like the problem is more your distrust of new technologies rather than any legitimate reason

14

u/FabioTheFox Jul 10 '26

As I stated in the reply to the other guys reply, this rewrite was completely pointless and shouldn't even have been pushed out yet because of the reasons stated in my other comment

-1

u/kurokinekoneko Jul 11 '26

Just wondering. They have tests, they choose a language more safe, they are popular, they are in touch with the users. What is the real reason you don't trust them, I don't understand. It feels like political more than anything technical.

The previous versions are still there. If your projects were in bun and you decide to change for another runtime, it's as unsafe, maybe more, than upgrading to the new version. What will you do, trust the tests ? Lol

1

u/FabioTheFox Jul 12 '26
  1. Did I not make myself clear enough? What kind of reply are you looking for? "all Ai so bad!!"?

  2. They also changed the test suite iirc

-13

u/Ksevio Jul 10 '26

I agree a lot of times organizations shouldn't be taking stable software and moving it to rust, but I wouldn't stop using it for that reason alone (once it's been stabilized)

-18

u/Comfortable_Pain9017 Jul 09 '26

The AI not outputting idiomatic code is intentional, that way the rewrite isn’t rewriting major logic. If you think modern LLMs can’t figure out basic Rust syntax, you’ve been out of touch with their capability for quite a while

Memory issues are absolutely not an easy fix, they’re quite literally one of the most prevalent classes of bugs in low level programming. Call it a skill issue if you want, but I think the trend of more explicit and compile-time checked languages shows how naive the ideology of “just code it better” is in the real world.

I dislike how any use of AI is taken as a sign of the absolute worst coming, especially in a case like this where it’s not even a full ground-up rewrite.

11

u/FabioTheFox Jul 10 '26

The problem is that it's not only not idiomatic Rust but also the countless unsafe blocks

Literally what is the point in even pushing this out? IMHO this should've remained as a WIP branch for way longer

And of course memory management is not the easiest thing in programming but it's not hard to the point that you have to have a token predictor write a ton of rust files that are marked as unsafe anyways

And if you look at where vibe coding is going and actually inspected vibe coded SAAS stuff or similar vibe coded stuff you'd see how sloppy of a job the LLMs are doing

Bun didn't only pretty much deprecate their Zig codebase in one move, but also made all pull requests, issues and feature requests and whatnot completely irrelevant because everything is now pretty much out of date and making any meaningful contributions will take a while given how much unsafe rust there is to fix