Agree with the parent. Regarding yarn, it was created because npm started showing weaknesses in many things, with large and complex dependency trees: install w

Agree with the parent. Regarding yarn, it was created because npm started showing weaknesses in many things, with large and complex dependency trees: install was slow, sometimes unreliable and not cross-platform portable, and the codebase was difficult to refactor due to legacy code and backward compatibility, so it made more sense to create a new package manager without that burden and try to iteratively align with npm to become a drop-in replacement. It's easy to fall into the fatigue due to new languages, tools etc. coming out each week but please think twice before posting dismissive comments like that. I observe a lot of "I don't read HN anymore" sentiment lately among top tech Twitter users, partially due to that. There's a lot of awesome stuff being given out for free and people are whining. (Yes, I'm a bit tired of constantly following and evaluating things, but I keep it for myself.) The situation came to the point where some guys are thinking about not opensourcing their tools anymore due to constant criticism and maintenance fatigue. Read the two links below (accidentally, the first one is from yarn co-author!): https://twitter.com/sebmck/status/879282797915119616 https://twitter.com/sebmck/status/879282797915119616 https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-an-open-source-maintainer/ https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-...