4 ms·

Python???! Python2 vs python3 is probably the worst thing I have ever seen a language do. Now teams are stuck supporting both versions, new devs are always con

Python???! Python2 vs python3 is probably the worst thing I have ever seen a language do. Now teams are stuck supporting both versions, new devs are always confused, teams can't upgrade, or if they do upgrade much of their python2 code is useless. The language is now filled with hacky crap: urllib, urllib2, urllib3 and ... AND python is slow. "That is the difference between having to look something up" PHP (for 15 years?) has had IDEs that fill it in for you.

bildung 7y ago
I am honestly confused how anyone could code themselve up into that python2 only corner. With the release of python2.6 and python3 in 2006, it was clearly described what one had to do to write upwards-compatible python2 code. 2006. https://www.python.org/dev/peps/pep-3000/ https://www.python.org/dev/peps/pep-3000/ No one had to have any problems with the transition. If they did, they had to willingly ignore the in-your-face documentation on the migration process.
- sinni800 7y ago
  But they did, and they will always do at every turn... I am not against making something not backwards-compatible. I am in favor of throwing old, bad things away even at the risk of having to rework some stuff... But how crazy legacy is at every damn company is just making it so frustrating. They will happily just wait it out for 14 years and then complain about their Python2 being desupported