Slashdot Mirror
ECMAScript 2016: New Version of JavaScript Language Released (softpedia.com)
An anonymous Slashdot reader writes: Ecma International, the organization in charge of managing the ECMAScript standard, has published the most recent version of the JavaScript language. ECMAScript 2016 (ES7 or JavaScript 7th Edition in the old naming scheme) comes with very few new features. The most important is that JavaScript developers will finally get a "raise to the power" operator, which was mysteriously left out of the standard for 20 years. The operator is **...
It will also become much easier to search for data in a JavaScript array with Array.prototype.includes(), but support for async functions (initially announced for ES2016), has been deferred until next year's release. "From now on, expect smaller changelogs from the ECMAScript team," reports Softpedia, "since this was the plan set out last year. Fewer breaking changes means more time to migrate code, instead of having to rewrite entire applications, as developers did when the mammoth ES6 release came out last year."
It will also become much easier to search for data in a JavaScript array with Array.prototype.includes(), but support for async functions (initially announced for ES2016), has been deferred until next year's release. "From now on, expect smaller changelogs from the ECMAScript team," reports Softpedia, "since this was the plan set out last year. Fewer breaking changes means more time to migrate code, instead of having to rewrite entire applications, as developers did when the mammoth ES6 release came out last year."
When somebody makes this "argument", it's a sure sign that they've never actually used Python, and that they're just spewing bullshit.
I am 100% sure I have done more with Python in the last few years than you will ever in your career, so, bzzt. There is a reason the most popular Linux server distros lag so far behind on Python versions - upgrading to a new version almost always breaks *something* in existing code. Have had it happen SO many times... (and I still use it! It's a decent scripting language for readable, modular projects. Doesn't mean it's that good at backwards compatibility compared to other languages...)
Anyone who has used Python knows that this is totally a non issue. PEP 8 [python.org] explains very clearly how to avoid and any all problems: "Use 4 spaces per indentation level."
THIS clearly proves you have no clue about any modern deployment techniques for HTML5 apps (minification, obfuscation, etc). Yes, of course you can minify Python, but it's just not going to be as efficient. But whatever. The fact is the current mainstream implementations are not designed for client-side browsers. Someone could build/integrate something (maybe PyPy?) but they haven't. Clearly there is a reason for that - and that is that Python doesn't really solve many of the problems people have with Javascript, so why bother?
I'm sorry, son, but you clearly don't know what the fuck you're talking about.
Oh fuck off. Feel free to post as non-AC, otherwise your opinion is useless. I have (non-Python) code used on many millions of consumer devices, and Python scripts on backend projects generating video content for those devices. Come back when you have ANYTHING useful to contribute to the discussion...