Meh. I’ve ported a fair many py2 projects to 3. At this point just bite the bullet. Even from a security standpoint. Trying to not let my bias seep through - but it’s been so long.

[–] [email protected] 15 points 1 year ago (5 children)

Ever worked on a giant corporate codebase? I'm not saying you're wrong, but corporate internals often work counter to common sense or sanity. You'll have a giant mess of code, that would require months of work to port. The longer you wait, the more expensive it will get, but if you just wait long enough, it might not be the current manager's problem anymore. So it will be postponed and postponed.

I've seen this in real life a few times. EOL driven development. You just wait until it's absolutely impossible not to upgrade, then you hastily stop everything, do the porting in a marathon of sadness that basically rewrites everything, and if you're done, you can wait for the next EOL.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

20 years on giant enterprise codebases. And any enterprise worth their salt at this point will be scanning these servers and flagging eosl software.

My experience the last five years of the 20 - security and service life trumps all fucking complaints about complexity.

To the point where it’s the opposite and I’m fielding weekly questions about why we’re still running an older 3.7.9 version. Among 50 other things.

[–] [email protected] 3 points 1 year ago

Yet, there are enough companies that simply don't care. Yes, that's bad, but it's also reality.

load more comments (3 replies)