upvote
A month before the rewrite I was hitting soundness bugs on fairly trivial JS code. I remember right, under HMR re-exports of module variables caused a snapshot, and importers of the reexport saw stale values.

I reported it, watched robobun write an unhinged +300 -0 patch which quickly got LGTM'd and merged.

I hope now that we've moved past AGI and into the ASI era things are better.

reply
I made a fairly straight forward webapp with Bun and let Claude check whether it was actually better than Node. Nope, Node consumed less memory and used about the same CPU as Bun. I didn't switch, because it costs tokens, but Node's reputation seem to be based on its legacy more than on today's use.
reply
"much much more lighter"? What does that even mean?
reply
You know exactly what it means. You're just being a pedantic ass to someone for whom English is not their first language

Ps to the original poster. I screw things like this up in my 2nd language all the time.

"more" and "-er" are sort of redundant. You could say

More light (but this is just awkward - you'd just say lighter).

Much lighter gives an extra degree of lightness than lighter.

Much much lighter even moreso. There's nothing wrong with saying it like this in an informal context like this, but it would generally be better to use words like significantly, vastly, enormously, slightly, a bit, considerably etc to modify the degree of "lighter"

Any LLM could explain the nuances of all of this in much much more detail (this actually makes sense, because detail is not -er).

English is difficult, but dont let that stop you - it is easy to communicate effectively with even a low degree of proficiency, when the other person is acting in good faith.

reply
No, I am literally asking you what you meant because I don't understand you. Are you talking about runtime memory usage?
reply
im not the person who you initially replied to... But surely it is self-evident what they meant by lighter (even if we dont know precisely what they were referring to) - CPU, ram etc... This is something that is always discussed when it comes to node vs bun vs deno
reply
Well, no. It's not self-evident even in your description of why you think it would be. CPU vs RAM is exactly the kind of distinction that I was trying to delineate. I've been benchmarking heavily lately as I'm working on a library, and anything that heavily depends on Crypto slightly favors Node. Bun admittedly does win on most things like JSON serialization & pure request/second throughput. However, it's just not clear cut enough to say that it is "much, much lighter" categorically.
reply