4 ms·
0. JS world is full of people captivated by shiny things. 1. yarn was a shiny version of npm 2. They did a Python 3 stunt (well...much worse) with yarn 2 so
by dboreham 3y ago
0. JS world is full of people captivated by shiny things.
1. yarn was a shiny version of npm
2. They did a Python 3 stunt (well...much worse) with yarn 2 so nobody uses it and everyone stuck with 1.x
3. Bugs aren't fixed in 1.x
4. So back to npm, or the next shiny thing.
Edit: no you can't switch back and forth. The tools end up storing internal state in your project repo. I mean, yes you can change, but it'll mean some hassle and possibly re-writing build files.
- fullstop 3y ago> 0. JS world is full of people captivated by shiny things. I mostly write C code these days, so I decided to checkout node to see what it was all about, and the shiny thing is spot on. A number of things that I looked at were described as "old" by people because they had been replaced by the new hotness a few months back.
- erhaetherth 3y agoDon't let that dissuade you too much. Yes, the community likes shiny, but you're not forced to upgrade if you don't like shiny. Just pin your versions and be happy.
- addicted 3y agoyarn 1 was meaningfully better than npm. And it was so much better that if they hadn’t pulled the python 3 but worse stunt I suspect a significant number of projects would have continued using yarn even after npm had caught up in terms of features and performance.