2 ms·
Large scale proof why this is a bad idea: Python 2.x vs Python 3 Those of you who don't know about this mess, it shouldn't be hard to find some rants by googli
by Too 13y ago
Large scale proof why this is a bad idea: Python 2.x vs Python 3
Those of you who don't know about this mess, it shouldn't be hard to find some rants by googling. Basically Python 3 broke backwards compatibility with python 2 without providing any compatibility layer at all, they just expected every third party library to switch "sooner or later". It's now 10 years down the road and nothing has really happened. Everybody who gets shit done is still using 2.x because they need the old libraries.
- Perseids 13y agoActually I see Python as a good example why you want to change. Python 3 has much cleaner concepts than Python 2: Strings are not byte arrays, use efficient generators by default, etc. On the other extreme take a look at C++: Lot's of ugly as hell syntax and pitfalls because of decades of backwards compatibility. See https://stackoverflow.com/questions/6939986/c-nested-constructor-calls-vs-function-declaration https://stackoverflow.com/questions/6939986/c-nested-constru... for an example of both. > Everybody who gets shit done is still using 2.x because they need the old libraries. And, btw., I hold each and everyone of these responsible as part of the chicken-and-egg problem.