Now, implementing the entire browser rendering stack just so the dev can use css and html to develop the UI, that's a different issue, but not really a javascript issue.
Also ES6 doesn't work in the browser (at least not reliably cross browser). We have to use it thought because it transpiles to something that works in the browser.
I think with another few years of the current progress javascript will be a good language - but there will still be a ton of old javascript to maintain which uses the principle-of-most-surprise syntax of older versions.
There are only two groups of people talking about this now, the poor folks who have to maintain and/or upgrade legacy software and you, people trying to stir things up.
Both these parties have existed in some form for absolutely every software upgrade ever so —as a community— we're past the point of caring. 6 years notice was more than generous and if they really want to drag it out longer, it's open source, but we'll be over here writing better, faster code.
If you want to go on and use Python3, fine. But no need to lie about the facts on the transition and that Python3 is better. It's simply different, technical churn rather than innovation.
Being fair, you're wrong on all fronts.
Our code quality has increased dramatically if only by being able to replace swathes of thread and Twisted glue with asyncio. The very same upgrades saw a ×10 runtime speed-up in some claggy mixed-layer code.
But even just comparing runtimes, 3.6 isn't slow[1]. They're about the same.
If your only opinion of Python 3 is it does unicode and it's slow, you may want to read the first line of the comment you replied to. Your arguments may have applied to Python 3.3 but they hold little weight in 2017.