4 ms·
That does not work when it's a programming language or a library because people depend on it and don't want to have 8 versions of the interpreter/vm to support
by gkya 9y ago
That does not work when it's a programming language or a library because people depend on it and don't want to have 8 versions of the interpreter/vm to support all the programs they may have that are written in that language. Rapid releases do work with applications.
- moron4hire 9y agoThen don't support 8 versions. Only support latest, unless they are paying you to do otherwise. Quit giving work away for free. But honestly, it's not that big of a deal. I've got code from v0.12.0 that still works on Node 8. People are making a really big deal out of nothing. The longer language developers hold back changes, the less time it gives language users to upgrade. What would you rather them do? Sit on defect and security hole fixes? Just because you're uncomfortable with the rapid pace of technology change? It's the Singularity dude. It's not going to slow down. You either learn to live with it or end up in the same pile as FORTRAN programmers.
- gkya 9y ago:) Yeah we live in a world of dual-option questions. I'm speaking from a users' point of view. If one program works on Node 8, other on 6, other on 0.12 sth., what do I do? Keep n runtimes for n programs? I don't know node, but I don't know C++ too, should I not use Firefox or Chrome then? Node runtime versions are unfathomable for those who don't develop on node, and thus as a user I avoid running node programs. Also, security fixes and bugfixes are expressed in semver w/ the last dot-seperated part of the number, the first number is the major version. If every fix breaks as much to bump up that number, then that's a bad sign too.