[coldtea]

>The same can be said thousands of 16 bit applications that are no longer supported on 64-bit architecture.

And some of those are a big loss as well.

But most of them are obsolete and deprecated (because e.g. Office suites, OSes and gaming moved on) in a way that Python 2.x programs used in businesses are not.

[Nadya]

>But most of them are obsolete and deprecated (because e.g. Office suites, OSes and gaming moved on) in a way that Python 2.x programs used in businesses are not.

Businesses that fail to adapt to changing markets/technology have nobody to blame but themselves when they've had 10 years to adapt or die. I struggle to find any sympathy for them outside of employees ringing the death bell who were ignored. Also, just to reiterate, 2.7 won't be going anywhere - businesses will need to accept it will cost them more to stick with it. That's the price paid for holding onto technical debt.

[coldtea]

>Businesses that fail to adapt to changing markets/technology have nobody to blame but themselves when they've had 10 years to adapt or die.

What "die"? Some of the companies using Cobol or other such older technologies (e.g. Java 1.4) are among the most valuable on earth.

And why should they adapt perfectly fine working programs? Just for the sake of it, or because devs like to rewrite stuff?

[Nadya]

>Some of the companies using Cobol or other such older technologies (e.g. Java 1.4) are among the most valuable on earth.

And they pay consultants and contractors in order to continue to do so. I'm not sure I'm seeing where the problem is? Want to stick with Python 2.7? Hire specialists. Problem solved. You just no longer get free labor from the maintainers of the language.