50 ms·
I like CoffeeScript and will continue to use it where appropriate. But I do wonder why we're stuck with all the cruft to let ECMAScript be backwards compatible
by smoyer 13y ago
I like CoffeeScript and will continue to use it where appropriate.
But I do wonder why we're stuck with all the cruft to let ECMAScript be backwards compatible. Couldn't we just one time introduce a few breaking changes to clean up the mistakes in the language's design?
And if you're really opposed to that, how about the same strict versus transitional semantics we use for HTML? I'd be happy to be writing code in a clean strict subset of JavaScript.
- roryokane 13y agoWe already have a strict subset of JavaScript, “strict mode” – see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions_and_function_scope/Strict_mode https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe.... You activate it by putting the code `"use strict";` at the top of a script or a function.