What's wrong with stability, LTS, and not fixing bugs for "compatibility".

[Ola Fosheim Grøstad]

On Thursday, 8 October 2020 at 10:37:22 UTC, FeepingCreature 
wrote:
> And no, big separations between major revisions such as LTS 
> versions are not a solution, they'd be contributing to the 
> problem. You think getting people to upgrade *right now* is 
> hard? Just wait until they have a reasonable expectation to let 
> upgrades lie for actual years. "If something is painful, do it 
> more often"; this aphorism is driven by the experience that 
> doing it less often makes it *more* painful. We risk ending up 
> in the D1 (Python 2, Perl 5) case where people don't update at 
> all.

Actually. That is a rather good solution. BTW upgrading from 
Python 2 would have been easy for me if it wasn't for the fact 
that service providers who use Python 2 change their service when 
switching to Python 3. Upgrading from Python 2 to Python 3 is 
easy.

Btw upgrading from an old C code base to C++20 is relatively easy 
too, but not if you want to upgrade to C++20 libraries.

So yeah, major versions work pretty good, if you have access to 
the same infrastructure after upgrading.