| ▲ | joshuat 5 days ago |
| This reads as another weirdly personal attack against Jarred for slighting a technology stack the author prefers, citing the even weirder personal attack against Jarred written by Andrew Kelley as the sole source to justify their "biggest worry", code quality. Idk why people have become so invested in this. |
|
| ▲ | jibal 5 days ago | parent | next [-] |
| The OP says > Unused code is one issue. A project called Buz[1] found over 11,000 lines of dead code from the Rust port.
[1]: https://github.com/jazzzooo/buz When in fact Buz is a fork of the pre-Rust Zig version of Bun. The OP has no credibility. |
|
| ▲ | hn_submit 3 days ago | parent | prev | next [-] |
| Jarred has probably already sold his company for big $$$ and is set up for life whether the Bun rewrite succeeds or not. We will, however, be left to scour the ruins of the financial devastation if this goes sour. |
| |
| ▲ | vrmiguel 3 days ago | parent [-] | | > Jarred has probably already sold his company for big $$$ He _has_ sold, though. Anthropic purchased Oven back in Dec. 2025. Or your probably was about whether it was big $$$ or not? | | |
|
|
| ▲ | potsandpans 4 days ago | parent | prev [-] |
| People _really_ don't want there to be success stories for llms and they will go through all lengths to discredit and disparage folks successfully exploring the space. |
| |
| ▲ | dafelst 4 days ago | parent | next [-] | | It is yet to be determined whether or not the bun rewrite is a success, though. | | |
| ▲ | hdjrudni 4 days ago | parent | next [-] | | Right. So let's hold our horses and wait for the release before disparaging anyone. I do have to agree with the author about Jarred's false claims about release dates though. Really not sure why he keeps doing that. | |
| ▲ | vga1 4 days ago | parent | prev [-] | | What are the standards for determining that? The most obvious benefit Rust can give them is being safe from memory leaks. This is hardly controversial: it has been a Zig design choice that memory leaks are the developer/user's responsibility. They have already demonstrated to have fixed several of those [0]. Marketing-wise, it has been an obvious success. Dunno if that matters. [0] https://bun.com/blog/bun-in-rust | | |
| ▲ | rcxdude 4 days ago | parent | next [-] | | Rust also doesn't prevent memory leaks: you can create memory leaks through reference cycles just fine in rust. | | |
| ▲ | vga1 3 days ago | parent [-] | | Who cares? | | |
| ▲ | zbentley 3 days ago | parent [-] | | People who don’t want to run out of memory? | | |
| ▲ | vga1 3 days ago | parent [-] | | Are the Rust programmers who suffered from memory leaks through reference cycles in the room with you right now? | | |
| ▲ | zbentley 3 days ago | parent [-] | | Yes? I’ve made that mistake, it’s not particularly hard to do. Stash an Arc in something that lives too long, or forget to clear its inner data structure when you should, and you have a leak. That’s not like … a design flaw or something, just a common class of error Rust can’t save you from. |
|
|
|
| |
| ▲ | andsoitis 3 days ago | parent | prev | next [-] | | > What are the standards for determining that? Seems pretty simple to me: if the software works, the port has been successful. If this is unsatisfactory, another way to think about the question is to ask "what would make you conclude it has failed?" That requires a sharp choice. | |
| ▲ | owebmaster 3 days ago | parent | prev [-] | | > Marketing-wise, it has been an obvious success. Dunno if that matters. What's interesting tho it's that it can go from apparent marketing success to a big failure as the release keeps getting postponed. | | |
|
| |
| ▲ | ofjcihen 4 days ago | parent | prev | next [-] | | Watch this: People _really_ want there to be success stories for llms and they will go through all lengths to discredit and disparage folks questioning the space. | | |
| ▲ | preg_match 4 days ago | parent | next [-] | | Both of these are true. I recall Anthropic's lofty claims about their C compiler. It just did not work, and they claimed all of this and that. It was clear they were driven to believe that agents alone could write a C compiler, and refused to believe they couldn't. Not that I think that AI couldn't write a C compiler. It definitely can... with a human at the helm and sufficient time. But, for people who don't like AI, they also refuse to believe that AI could be good at any particular workflow. Which is just obviously not true, there are workflows that AI is really good at. Language re-writes are one of them. They're almost mechanical in nature and trivial to check via tests. So, the perfect use-case for an LLM. I'm not saying the Bun re-write is any good, but the underlying concept is sound. If ever there was a tool to do a language re-write, it would be a high quality LLM. | |
| ▲ | 4 days ago | parent | prev [-] | | [deleted] |
| |
| ▲ | bmitc 4 days ago | parent | prev | next [-] | | It isn't LLMs in general, from what I can tell. It was how this port was done and communicated. | | |
| ▲ | cheikhcheikh 3 days ago | parent [-] | | It was communicated fine, can you be more specific ? | | |
| ▲ | bmitc 3 days ago | parent [-] | | No, it wasn't. For example: https://news.ycombinator.com/item?id=48019226 | | |
| ▲ | cheikhcheikh 2 days ago | parent [-] | | you really went digging with that 3 months old hn comment. What's wrong with that comment btw? Are you saying he was lying and they did in fact commit to the rewrite at that point? | | |
| ▲ | bmitc 2 days ago | parent [-] | | I didn't dig. It was prominent at the time this occurred, because like I said, it wasn't communicated at all until they were already in the middle of it. And yes, I think he was not genuine there and that they had indeed fully committed to the rewrite prior to that point and comment. If you're not aware of any of this, how are you arguing it was communicated clearly? |
|
|
|
| |
| ▲ | itemize123 3 days ago | parent | prev [-] | | but, importantly, it is not the main reason why people are skeptical of bun rewrite right |
|
