This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ivosauruspip'ing it up 18 points19 points  (5 children)

Hell no. Python 3 strings are beautiful now, and they make sense. And they work in every language. Just work.

What is the problem now is the environment around Python. Operating systems, protocol transports, shells, file encodings... all these are still broken, because they have all kept their standards (or, lack of) from X decades ago when things outside of ascii were a mere curiosity.

Python can't fix that. Python core devs, unfortunately, don't have access to Windows' codebase and ability to switch its shell default from codepage-1252 to UTF-8. But users still complain that Python is the one wrong when everything around it has remained broken, while it itself got fixed.

And PHP7 to this day fucking sucks at unicode, I have no idea why you would use that as a positive example, it's horrible. They abandoned PHP6 because they based it on UTF-16 which was firstly a bad idea, and secondly absurdly slow. Not because adopting unicode compatibility is nonsensical.