News for hackers. Stuff that matters.
Re:Yarn – A new package manager for JavaScript by BinaryIdiot on Tuesday October 11, 2016 @01:23PM (#12686442)
I'm glad they're okay with it but then again what else would they post? npm has some major, major issues with it and it has barely moved in years. This Yarn looks like it solves quite a few issues with npm and it took another company to build it.

That's insane. It wouldn't surprise me if yarn becomes popular and its proxy to npm slowly turns off and boom, everyone would be migrated and npm would be left with little to no users. Yeah that's probably unlikely for the immediate future but Yarn is positioned perfectly to siphon off npm's users very painlessly.

Re:Yarn – A new package manager for JavaScript by sotojuan on Tuesday October 11, 2016 @01:27PM (#12686481)
Does anyone know why npm moves so slowly?
Re:Yarn – A new package manager for JavaScript by softawre on Tuesday October 11, 2016 @01:53PM (#12686766)
they have millions of installs and can't break them?
Re:Yarn – A new package manager for JavaScript by striking on Tuesday October 11, 2016 @02:01PM (#12686863)
Well, but remember that time they shipped an SSL cert that broke all updated clients? I'm not sure they move slowly because they don't want to break things, because that would have been a pretty easy bug to catch...

http://blog.npmjs.org/post/78165272245/more-help-with-selfsi...

Re:Yarn – A new package manager for JavaScript by ssunstruck on Tuesday October 11, 2016 @02:32PM (#12687211)
That's not really a good counter example. It's more of a mistake on a release...
Re:Yarn – A new package manager for JavaScript by striking on Tuesday October 11, 2016 @04:05PM (#12688058)
It's more of a failure to double check that npm runs when you change the SSL cert you bundled with it.

I think it's a great example of moving a little too quickly, honestly. Especially since it bricked plenty of npm installs instead of being "just another bug".

Re:Yarn – A new package manager for JavaScript by BinaryIdiot on Tuesday October 11, 2016 @04:39PM (#12688333)
Do they necessarily have to break them to move faster? It's a package installer. Yarn is handling locking / shrinkwrapping different but I would argue shrinkwrap needs to be abandoned and re-done anyway so I'm not seeing the risk. It took them, what, two years just to flatten dependencies and move to npm 3? That was actively breaking Windows usage of node!

I love the service they offer. Not a fan of the tools or pace. Npm comes in the node installer so why do they even have to care about improving?

Just my thoughts.

Re:Yarn – A new package manager for JavaScript by Jean-Philipe on Wednesday October 12, 2016 @11:52AM (#12693939)
What do you mean by moving slowly? IMO there's not much to add. I'd like to see some speed improvements, but otherwise I'm not sure npm should evolve.
Re:Yarn – A new package manager for JavaScript by secoif on Tuesday October 11, 2016 @06:40PM (#12689112)
technical debt and not wanting to break people's workflows
Re:Yarn – A new package manager for JavaScript by LunaSea on Tuesday October 11, 2016 @03:48PM (#12687928)
Because they focused on hiring SJW profiles that write codes of conducts and readme's all day long instead of actually software engineers that could improve the tool.
Re:Yarn – A new package manager for JavaScript by sctb on Wednesday October 12, 2016 @02:42PM (#12695456)
Please resist the temptation to glom ideological snark onto unrelated threads. That's not what this site is for and it ruins threads for everyone by being simultaneously distracting and boring.