This probably comes off as said from an ivory tower, but I don't think it's the people from other untyped languages who hate JavaScript nowdays. ES6+ looks pretty good compared to Python/Ruby/PHP perspective, and it works in the browser!
I don't hate javascript for its quirks or implementation details, I hate what it has done to the experience of browsing the web, and now what it is doing to desktop software.
Some of my hate has been lessened after looking at microsoft's own benchmarks. NodeJS performs much faster than ASP.NET 4.6 + IIS. Core improves on this, but the point is after all these years writing .net applications I knew they weren't native performance but they were good enough. I didn't know javascript was just as good or even better in some areas.
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.
ES6 is nice compared to PHP. It is not close to Python yet in terms of consistency and it-just-does-what-you-expect syntax. ES7 etc may get there but the standard library is also still lacking.
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.
2011 called, they want their anti-Python nonsense back. Python 3 won. It's leaps and bounds ahead of 2.7 at this point and it's moving in a positive direction.
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.
Being fair, he is right. So grant him that. Python3 didn't really win. Lots of people jumped to TypeScript, Go and other stuff as a result. I wouldn't say you're writing better code, faster code either. Python2 supported unicode if that's the concern, and as of today the 2.7 interpreter is still faster than 3.6.
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.
This is hilarious. How are you judging the quality or performance of my code again?
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.
Unfortunately for you the facts aren't on your side. Python2.7 is still faster. People like you have said "your arguments hold little weight in 2013" too. Python3 was released in 2008, it's been 9 years and it's still a failure. The OP was correct and you were wrong. It's a shame that bothers you so much.
My experience is in predominately dynamically typed languages and I loathe JavaScript because of its implicit conversion of everything to strings, its substandard and clunky prototype object system, and that it's the only option that's cross browser compatible. For the record: I like Python, have no experience with Ruby, and dislike PHP.
