4 ms·
This is why you should choose a frontend framework with a LTS (long-term support) program. (For example, Angular 4 or Ember.) You don't have to upgrade to the l
by blktiger 9y ago
This is why you should choose a frontend framework with a LTS (long-term support) program. (For example, Angular 4 or Ember.) You don't have to upgrade to the latest version of the framework, just the latest LTS version which will have all the relevant bug/security fixes. Only when the framework starts to drop support for the LTS version do you have to deal with upgrading and learning whatever new features they have added since then.
- tobltobs 9y agoMaybe it is worth to add that a LTS release in JS land isn't what non JS developers would expect. LTS releases with support for 6 months? Seriously?
- Spivak 9y agoFor comparison Red Hat supports their servers for a minimum of 10 years and you can buy extended support after that.
- Cacti 9y ago6 months for v.4, then 1 year. Which is still absurdly short. That's not even long enough for sane, normal versioning (e.g. Python 2.6 through 2.6.9 was like 5+ years). These people are crazy.
- blktiger 9y agoFor Ember at least, the LTS is 4 releases, however all versions are backwards compatible up to the point at which they bump the major version. So you can just keep upgrading whiteout changing code for potentially years.