Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm curious as to why yarn instead of contributing to NPM? I am aware that yarn was the inspiration for many improvements for NPM by providing an alternative, but going forward do we need two systems? Is the plan for yarn to be compatible with NPM and package.json?


From what I've heard, the Yarn codebase is much cleaner than NPM. If anything, I think it would make more sense to migrate NPM over to yarn


Yes, having competition here has clearly benefited the ecosystem.

I wrote a recent comment comparing the history and goals of Yarn and NPM:

https://news.ycombinator.com/item?id=18950012


I've been using both for a while and I'm happy with their decision not to try and be "compatible" with NPM. I'm also pretty happy with using Yarn only - things are just faster and in reality make a little bit more sense.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: