@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 NPM Inc was internally in a certain kind of shape when Yarn came out. Its release shook things up in a very serious way and caused me and others a LOT of stress, and some of the most regrettable overworking I've done in my entire career, but it did directly lead to NPM@5 and subsequent perf improvements.

I think the thing that Yarn really did for us (us being the NPM team) is that it taught us that what people actually give a shit about is performance, not things being bug-free, or featureful, or cross-platform. As long as you can say your thing goes really really fast, people basically go ga-ga over it and forget all the other things that matter. They will put up with absolute trash in order to get those speed gainz (and, frankly, Yarn was a broken piece of shit when it first launched and you can't convince me otherwise). Heck, even Yarn's "ergonomics" being an improvement seems like bullshit to me.

All people actually wanted was a faster package manager, and as soon as they got that, they stopped caring about Yarn, except for the folks who had already made the switch and didn't really have a reason to bother switching back.

@reconbot @brianleroux it’s the worst burnout I’ve experienced in my entire career and the most stressful several months where I felt there was an existential threat to my job if I didn’t work 12-15 hour days to get npm5 out.

Never again

@zkat @reconbot @brianleroux I'm still sore about the whole "yarnpkg registry aliasing the public registry at the CDN level" thing.

The teapot outage happened because of that proxy: our CDN had to add an exception to allow proxying between the yarnpkg domain and registry.npmjs, since they hosted both. Our CDN recommended we add strict host header checks to our worker. To my (dis-)credit, I flubbed this.

One yarn maintainer was publicly unkind about this in a way that still gets me angry.