141–150 of 153 posts
Earlier quoted context omitted.
People who don’t want to run out of memory?
Are the Rust programmers who suffered from memory leaks through reference cycles in the room with you right now?
That’s not like … a design flaw or something, just a common class of error Rust can’t save you from.
I've been a heavy user of Bun since 2022. The last three months of their public timeline have not looked good, so I wanted to summarize my frustration
Earlier quoted context omitted.
That's a fair criticism... they move slower but mostly because they were the first. They would have to build a new Server and Request/Response primitives from scratch, or deprecate what they already have, or somehow shoehorn the existing types into the new ones. They do seem to have just merged in support for Web Workers though, which I've been following for a while: https://github.com/nodejs/node/issues/43583 So I d…
Same thing can be said about Streams in Node.js as well. They had a working streams implementation before the Web Streams API was in browsers (iirc). So implementing the standard now means removing what's already there, or breaking a lot of existing code. Which leads to confusing things like the fact that there are two streams APIs in Node now: Streams: https://nodejs.org/docs/latest/api/stream.html Web Streams: http…
When we used to code by hand, Bun used to have an amazing list of articles on how to convert from almost any kind of streamable to almost any other type. I used it a lot, and that was when I started liking Bun so much.
Lol Bun rust-rewrite is still not released even after 3 month :).
I'm still waiting for someone to bring forth some reproducible stats and state something along the lines of "I did a comparison of Bun 1.3 vs 1.4, and found these user-affecting issues in the latter which are not in the former".
Is it a paid job?
For the internet at large no, but the comment doesn't make sense. It's not as if volunteers don't post all kinds of checks, and reports, and benchmarks, and deep dives anyway.
Lots of people are apparently happily using the canary version in prod. Anthropic has been using it for ages now, as has Prisma. Why not release 1.4 (or 2.0 or whatever) then? It won't get picked up by lots of tooling and won't get allowed in many "no pre-release in prod" shops until then. It had plenty of issues before (many thousands of open issues) so a few thousand more is hardly a big deal...
TFA shows that they are working on releasing it. If you actually want an answer to your question, ask Jarred ... you won't get it here.
Earlier quoted context omitted.
It was communicated fine, can you be more specific ?
No, it wasn't. For example: https://news.ycombinator.com/item?id=48019226
Earlier quoted context omitted.
No, it wasn't. For example: https://news.ycombinator.com/item?id=48019226
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?
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?
Earlier quoted context omitted.
Isn't supposed to be faster with LLMs?
The rewrite was a lot faster. Actually shaking out the bugs from the rewrite (or just getting enough confidence in the new version from use by early adopters) is probably not going to be drastically faster.