That may be true in the case of smaller open-source things. But when it comes to larger projects, it's largely the same way as it is in the rest of our society: things that are considered too important to the whole are changed regardless of pushback.
Not a big deal if something like screen dies or fades. But the same is not true of something as big as Python.
Open-source is democratic in that you have a voice, but it doesn't mean your opinion matters much in certain cases.
Python2 hardliners have been warned for years. By the time it is sunset it will have been 12 years since it's release. Why should the Python devs stop moving their project forward because you're not interested refactoring and deprecating old code?
Where I work we move forward and adapt our code/patterns over time. If an old thing breaks (due to updating to Py3 compatible features), we deprecate/replace or refactor it to work, whichever the team decides holds more value for us as a group. There's probably very little code in there that was written 8 years ago when Python3 dropped. We iterate forward.
I get pretty frustrated by this "but this stuff I wrote a decade ago works and I don't wanna..." attitude in the tech world. Not saying people should burn the candle at both ends to keep up, but come on. 12 years and you can't refactor forward? Then you find yourself in a position where, oh shit we really have to burn the candle at both ends.
This isn't about the actual work involved then. Because you're going to write code anyway. It's about not wanting to change your headspace (not all that much, esp for experience programmers) to write Python3 compatible code. The burden then is on Python hardliners to keep up or fade away, much in the same way you suggest.
Old is replaced with new. It's the way the world works. Get over it.
Not a big deal if something like screen dies or fades. But the same is not true of something as big as Python.
Open-source is democratic in that you have a voice, but it doesn't mean your opinion matters much in certain cases.
Python2 hardliners have been warned for years. By the time it is sunset it will have been 12 years since it's release. Why should the Python devs stop moving their project forward because you're not interested refactoring and deprecating old code?
Where I work we move forward and adapt our code/patterns over time. If an old thing breaks (due to updating to Py3 compatible features), we deprecate/replace or refactor it to work, whichever the team decides holds more value for us as a group. There's probably very little code in there that was written 8 years ago when Python3 dropped. We iterate forward.
I get pretty frustrated by this "but this stuff I wrote a decade ago works and I don't wanna..." attitude in the tech world. Not saying people should burn the candle at both ends to keep up, but come on. 12 years and you can't refactor forward? Then you find yourself in a position where, oh shit we really have to burn the candle at both ends.
This isn't about the actual work involved then. Because you're going to write code anyway. It's about not wanting to change your headspace (not all that much, esp for experience programmers) to write Python3 compatible code. The burden then is on Python hardliners to keep up or fade away, much in the same way you suggest.
Old is replaced with new. It's the way the world works. Get over it.