Rich client side web apps gone too far (2014)

Re:Rich client side web apps gone too far (2014) by orangecat on Saturday March 28, 2015 @08:58PM (#9283446)

Unicode support out of the box

utf16 support, which isn't the same thing: https://mathiasbynens.be/notes/javascript-unicode

easy manipulation of strings, arrays, and dictionaries

JS objects aren't dictionaries; all keys are coerced to strings, they lack basic operations like getting a list of keys or values, and iterating over keys can bite you if you forget hasOwnProperty.

Python comes pretty close, with slightly wonky scoping and Unicode bolted on

And equality operators that aren't utterly insane, a usable standard library, local rather than global scope by default, classes, namespaces, modules...

ES6 does look a like a large improvement. Mainly because it fixes misfeatures and adds capabilities that better languages dealt with years ago.

[ Parent | on HN ]

Re:Rich client side web apps gone too far (2014) by chase-seibert on Saturday March 28, 2015 @11:47PM (#9283794)

ES6 admittedly borrowed a lot from Python. I just wish Guido had been successful getting Python supported as a first class language in Chrome; that might have actually given us a choice in the browser. Even then, I find it hard to imagine that ALL other browsers would have followed suit.

[ Parent | on HN ]