you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 7 months ago

The Python 2 to 3 migration dragged on for nearly a decade because ecosystem fragmentation was the real problem, not print syntax. Entire codebases had accumulated that depended on libraries dead or unmaintained, and rewriting everything while staying competitive was not realistic for most teams. That collective inertia is not something frameworks fix retroactively with a 'just migrate' message.

  • source