Re:Fix the versioning
by jessaustin on Friday August 29, 2014 @06:55PM
(#8244888)
...having a version 47.0.0 and such doesn't seem all that terrible to me...
What would the effect of that be? Since few people are silly enough to use the ">=" operator in package.json, a popular package with that many "breaking" changes is effectively going to be pinned at 46 different points. I imagine we'd start to see some of the same entitled whinging we see exhibited here, but in the opposite direction. "Why do you have so many major releases? It means I have to re-release my packages constantly."
That's a fair point. I guess a better solution in my mind is teaching people to be more responsible with their package.json file and consumption of packages (ie reading changelogs), but that's not jashkenas' problem, nor should it be.
Re:Fix the versioning
by jessaustin on Friday August 29, 2014 @11:46PM
(#8245579)
Actually I think he's done quite a bit of teaching along those lines in the last three days. Several students seem unhappy with the lesson...
This is the most depended on module on npm. Why are you so intent on alienating the package consumers? IMO, having a version 47.0.0 and such doesn't seem all that terrible to me, and is still just as human readable. Other groups are doing it and it's working just fine (ie Chrome).