Yarn – A new package manager for JavaScript
I use JS+Node+NPM for my day job and many side projects.<p>Initial thoughts:<p>- Why didn&#x27;t Facebook contribute the updates to NPM directly?<p>- They are coupling a package manager and registry proxy; the latter has many existing implementations already<p>- The differenced between Yarn and NPM+Shrinkwrap do not seem substantive; NPM made the design decision to use a sometimes non-deterministic install algo in NPM3 to speed up install times - when network is involved, there is a serious trade off between idempotency and speed<p>In general, FB seems to love building their own versions of existing tools:<p>- Flow, introduced 3 months after TypeScript<p>- Nuclide instead of Atom&#x2F;Sublime&#x2F;VSCode<p>- Jest instead of Jasmine&#x2F;Mocha<p>- DraftJS instead of (insert of of the existing 100 text editors here)<p>- ...<p>I get that these are useful internally at FB, but I don&#x27;t think they help the community much. It would be better to work with existing tools and contribute back to them than to reinvent the wheel every time something doesn&#x27;t work perfectly for their use case.<p>I get that FB uses these as recruiting tools, it&#x27;s useful for them to have rights for these projects, and it gives their engineers something to do and be excited about, but I do not want a whole dev tool ecosystem controlled by big FB.<p>Also, I find IED&#x27;s approach to speeding up builds far more novel and interesting - <a href="https:&#x2F;&#x2F;github.com&#x2F;alexanderGugel&#x2F;ied" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;alexanderGugel&#x2F;ied</a>