4 ms·
My biggest issue is that Python 3, from an outsiders perspective, does not look at all like it's about unicode. Python 3 could very well have been done in a way
by gravypod 10y ago
My biggest issue is that Python 3, from an outsiders perspective, does not look at all like it's about unicode. Python 3 could very well have been done in a way that just fixed the back end implementation of python 2 (implement a string as an extension of a list) and then most things would have probably worked fine. Just handle all the unicode stuff in the back end and treat them the same exact way as Python 2 treated strings.
That's not what happened and instead we had a huge change to one of the fundamental data structures of any programming language and a lot of changes that pretty much no one wanted.
Packages were moved, things were renamed, etc. These are not changes that should be made. Make a fix, don't make me rewrite my code because someone else said "Eh, I like this name better". It's useless to do so and helps no one. There are now swaths of community-written documentation that are useless because every package name in the post has changed for seemingly no reason.
The issue is simple: it could have been handled so much better.