1 karma · joined January 20, 2020
this portrayal of the python 2 to 3 migration does not represent the majority of the community! and yet we keep hearing it over and over because "large" codebases were not migrated on time.
this migration was a software engineering problem. i hope by now, people have learned to write dumb code and avoid clever tricks whenever they can. performance and clever tricks get tied to languages, OSes, & hardware versions. python is no exception!
not saying don't do them. just saying know what you are getting into.
again, the issue is not entirely due to breaking changes. but python made it too easy. c++ for example would have given people such a hard time that they wouldn't have even bothered. python's was too permissive.
i have seen the python 2.7 codebase that shipped with the original appengine. it always felt like traveling to a different world whenever the debugger gets into their code...
yea and totally broken UI on mobile. not their fault though. is it time for browsers to adopt a sensible default CSS for mobile?
inbox was email that simply worked. never got in your way. not for the "pros", that's what gmail is for. it had its place. and yet...
wait wuh? i thought these were just two of the dozen variants of the BASIC dialect... interesting!
not to pick on sentry here, but you know, my experience is that people are having a hard time migrating due to them using obscure tricks and features of python 2.7. so their code is breaking because the language evolved.
the saying goes write dumb code or something because debugging is twice as hard. if there is anything to learn from all this, it's to write dumb code because maintenance is twice as hard too.
that's all that is happening really!