Sick of Ruby, dynamic typing, side effects, and object-orientation (2014)

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by orf on Tuesday November 07, 2017 @05:29AM (#15642241)

> Yarn is a perfect example. It came out very recently, relatively speaking. And yet it's clearly the future.

Node threw themselves into Semver, and it was supposed to be great. Nobody needs a lockfile because everyone obeys semver, so every time you do 'npm install' your app is guaranteed to work because everything is semver'd!

Oh wait, no, that didn't work out. Better freeze every dependency and sub dependency because who knows what will break when we update!

This is why throwing yourself at whatever shiny new thing without thinking or looking at how other languages do it is not always a great idea.

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by n3dst4 on Tuesday November 07, 2017 @06:22AM (#15642472)

To be clear though, npm and yarn have not abandoned semver. Semver is still a good way of expressing dependencies. It's just that there are enough cases where it's not sufficient, and that's why lock files are in fashion this season. The underlying semver data is still there though, which is different to the sort of package manager which only records installed versions.

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by orf on Tuesday November 07, 2017 @06:57AM (#15642631)

Sure, I didn't meant to imply they abandoned it. I simply meant that in a perfect semver world you wouldn't need lockfiles, except maybe in special cases.

[ Parent | on HN ]