4 ms·
Not everyone is down to switch such a core piece of the infrastructure at the first sign of new and shiny. I think yarn will succeed, but so did lots of people
by mattnewton 10y ago
Not everyone is down to switch such a core piece of the infrastructure at the first sign of new and shiny. I think yarn will succeed, but so did lots of people about bower, ied, duo, etc.
Give it a moment to settle. The path forward might even be a merger instead of replacement.
- terink 10y agonode developers have overwhelmingly indicated that they want to switch to yarn and are willing to work through the short term problems until it becomes stable. npm wouldn't be a suitable caretaker for yarn.
- franciscop 10y agoI am sorry, but what? What is your source? From a new account[1] with only 3 comments overwhelmingly favoring yarn over npm it's difficult to trust this as it just seems like SPAM. I have been developing in Node over 3 years and trying new things constantly and no, I'm not really excited about yarn. Nor many Node developers I know. [1] https://news.ycombinator.com/threads?id=terink https://news.ycombinator.com/threads?id=terink
- terink 10y agoMost devs on Github disagree with you: https://github.com/yarnpkg/yarn https://github.com/yarnpkg/yarn - 17,271 stars https://github.com/npm/npm https://github.com/npm/npm - 10,807 stars
- franciscop 10y agoAh I see, Github stars. I am not sure they are a good indication though; many people (HN effect?) star something new and fancy when it comes out, while I think NPM can be considered to have "grown" organically with Node.js; which in my experience doesn't attract as many stars at all. When NPM came out the Node community was still in its infancy, with not so many people in the ecosystem. I haven't even starred NPM while I almost starred Yarn the other day.
- deleted 10y ago[deleted]