3 ms·

I'm still skeptical. Webpack is one of the saner ones. Many JS libraries are still doing break-everything major version releases- Babel and Angular come to mind

by tboyd47 10y ago

I'm still skeptical. Webpack is one of the saner ones. Many JS libraries are still doing break-everything major version releases- Babel and Angular come to mind.

whostolemyhat 10y ago
That's what a major version is supposed to signify though, isn't it? Most JS/NPM-based projects use semantic versioning, so a major version update means breaking/backwards-incompatible.
- tboyd47 10y ago
  Even if it's communicated correctly, it's still a hassle.
  - whostolemyhat 10y ago
    Are you complaining that things get updated? You don't have to use the absolute latest versions of everything, you can still use older versions if you want.
    - deleted 10y ago
      [deleted]
    - jameskilton 10y ago
      Caring about upgrade paths is super important to the longevity of a project. See: Python 3 vs Ruby 2 adoption. Taking the mentality that "I can break everything and just bump the major number" will lead to a project that either 1) is no longer is used by many people or 2) is a maintenance hell because people are staying on old versions and asking for bug fixes and improvements.