Downvoted for surprising lack of substance. Note I do read many of your blog posts -- and thanks for writing them, there is a lot of insight for me. I also di

Downvoted for surprising lack of substance. Note I do read many of your blog posts -- and thanks for writing them, there is a lot of insight for me. I also did read most or all of your blog posts about python3 unicode handling. The thing is, while most or all of the facts presented there are "true", many of the negative conclusions there are just your opinion that stems from years and years of doing it "your way" (I would call it FUD, but I have strong opinions too). Python2's unpredictable implicit conversions are hardly "sane" (that's one of the unjustified claims made there). Do you also call Javascript's "==" sane? For me Python3 str has worked like a charm for years. I like the strict separation of high and low level affairs. I like how I can treat files as text files (deal only with python3 strs) and don't have to think about low level affairs, or types, or conversions, which is a great boon for scripting. I like how I can drop down to the bytes level when needed and know exactly what I'm at. For some balance, I wouldn't expect that conversion to python3 is always easy. But I would blame python2 for missing clean concepts, not python3. Also, it's hardly convenient to code most of a Python3 app at the byte level. But it could be argued that python should not be used for these things.