Hacker News new | past | comments | ask | show | jobs | submit | 0xptr's comments login

Speed wise npm@5 caught up a lot of ground. Iirc it was the same a while ago. However, I always felt like the release was a bit rushed. I sticked to Yarn too tho.


This is so completely and utterly wrong, unfortunately...

Yarn takes 12 seconds to install all of our node_modules, npm@5 (latest) takes over 12 minutes.

This made it completely and utterly untenable for our CI system, so we switched to yarn and shaved 12 minutes off our CI builds. It's been fantastic.


That's got to be down to caching. What's the difference if the yarn cache is cleared?


25 seconds when the yarn cache is cleared... downloading is not the slow part here.

Old results from about a month ago:

https://twitter.com/bertjwregeer/status/887450964420055043

  npm 5.3.0: added 1991 packages in 538.289s  
  yarn v0.27.5: Done in 58.42s.


I guess I should photoshop more people in my stock facebook placeholder :^(


I second this.

We used to hire on Upwork regular for bigger projects and it usually was close to a gamble (for both parties). You get > 30 applicants easily if you pay decent wages and the cv's are usually quite non saying.


We gave people small, test projects to see if they could deliver and communicate effectively (they didn't know it was a test .. we paid them of course). Been having a decent experience on Upwork so far from the hiring side (we started this year). If you found resources on how to use Upwork more effectively, would appreciate pointers :)


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

Search: