3 ms·
If you are at 5.x today, and 6.x sometime next year, as a library author why would you - next year - decide to write a package for something for 4.x? That is 2
by foolfoolz 11y ago
If you are at 5.x today, and 6.x sometime next year, as a library author why would you - next year - decide to write a package for something for 4.x? That is 2 major versions outdated. If it's really major bumps every 6 months and 7.x comes out next year too, who's going to be writing new stuff for 4.x? Most new packages will probably support the current version, and then your LTS window of 2 years doesnt mean much.
- dragonwriter 11y ago> If you are at 5.x today, and 6.x sometime next year, as a library author why would you - next year - decide to write a package for something for 4.x? Because the target user community of what you are writing consists of the kind of users that are likely to use LTS releases. > Most new packages will probably support the current version, and then your LTS window of 2 years doesnt mean much. You don't choose LTS because you want support for every new packages that haven't been written yet on the day they come out, you choose LTS because you've got something for which you want to have a stable platform with bug fixes, rather than an unstable platform with breaking changes, and are willing to not have access to the newest platform features or the newest third-party libraries that depend on them to get that stability.