4 ms·

Some people share this view. http://avodonosov.blogspot.com/2014/08/semantic-versioning-is-not-solution.html http://avodonosov.blogspot.com/2014/08/semantic-ve

• yardstick 3y ago
  I would contend that this is an issue with namespace collision / poor namespace management than it is an issue with semver. For example when I have a REST API endpoint I always prefix it with /<module>/<major-version>/ - would never expect to host both old and new versions on the same base URL
• 8n4vidtmkvmk 3y ago
  Well they're wrong and so is their language of choice. Any language that pollutes the global namespace when you import a lib did it wrong. For all of JS's faults, they nearly got this one right. Also, even in JS this is still a problem when you really do want all packages to share the same version of the lib, regardless if you're able to import multiple. Sometimes you just don't want multiple instances. Npm and yarn offer a solution for that too, by forcing a certain version resolution but that then you're on your own if it isn't compatible.
  • avodonosov 3y ago
    A related reply: https://news.ycombinator.com/item?id=37762843 https://news.ycombinator.com/item?id=37762843