31–40 of 69 posts
This is why I hate ES6. JavaScript used to be a write once, run anywhere language. We sacrificed that for syntactic sugar.
Dumb question, from someone who doesn't work with Node.js: Why are there 32 versions of it?
There are actually 303 versions of node (including iojs, according to the Node Version Manager): $ nvm ls-remote | wc -l 303 Most of those are patch releases. There are 47 minor releases and 6 major releases: $ nvm ls-remote | grep -oE 'v\d+\.\d+' | uniq | wc -l 47 $ nvm ls-remote | grep -oE 'v\d+' | uniq | wc -l 6 Most language implementations probably have similar number of releases.
It however doesn't execute the containers simultaneously, that is really cool!
An aside - over the last few months I began running my containers on two popular CI services and have had some serious pain. I have a slight feeling you will regret the words: "works well with CI as well!"
Dumb question, from someone who doesn't work with Node.js: Why are there 32 versions of it?
There are actually 303 versions of node (including iojs, according to the Node Version Manager): $ nvm ls-remote | wc -l 303 Most of those are patch releases. There are 47 minor releases and 6 major releases: $ nvm ls-remote | grep -oE 'v\d+\.\d+' | uniq | wc -l 47 $ nvm ls-remote | grep -oE 'v\d+' | uniq | wc -l 6 Most language implementations probably have similar number of releases.
https://clojure.org/community/downloads_older http://www.scala-lang.org/download/all.html https://www.python.org/downloads/
etc...
Dumb question, from someone who doesn't work with Node.js: Why are there 32 versions of it?
I know that other languages also have issues in this regard -- but for more mature languages it seems to be more an exception than than the rule (restricted to certain platforms of subsystems, say).