Lots to unpack here. Modern JS going just great.

This situation is avoidable

https://dev.to/thejaredwilcurt/bun-hype-how-we-learned-nothing-from-yarn-2n3j

Bun hype. How we learned nothing from Yarn

Here we go again, making the same mistake. I'm constantly reminded that every 5 years the amount of...

DEV Community

@brianleroux I really liked the fork of io.js what we got in the end was so much better node v4 was way beyond 0.12 the previous release. I’m also not convinced and npm would’ve gotten as good as it did without yarn. The tribalism and the incompatibilities are troubling. But the years it took npm to catch up are probably why yarn never shut down. Deno on the other hand has made node better, but I’m not tapped into its trajectory. It’s absolutely not like io.js.

Bun seems like a toy tbh

@reconbot @brianleroux whooooosh! I'd totally forgotten about iojs. ....am I.... old?
@morgan @brianleroux remember that rails fork around the same time? Forced rails to get better iirc, the merges of these projects were amazing times.
@reconbot @brianleroux thankfully no, I was already so fed up with rails at that point in time I was paying no attention to its ongoings. Then thankfully node came along saved me from my homegrown jetty/bayeux/rhino abomination.