Too much blank-slate-ism here for me. ES5 strict was not the opportunity:
1. The clock would have to go back much farther if people actually wrote
a < b < c, but we still lack evidence that this is much used. It *could*
be, so we're loath to change its semantics incompatibly (and we won't
want opt-in versioning, or "modes")...
2. Just deprecating is not enough, especially if the feared "misfeature"
from C via Java is not actually misused. We'd want to obsolete, to clear
the decks for Pythonic chaining. But that is not in the cards (see 1).
/be
Tom Van Cutsem wrote:
2013/7/24 Forbes Lindesay <[email protected]
<mailto:[email protected]>>
Perhaps there should be a spec somewhere for "misfeatures" like `a
< b < c` which linters ought to all reject. It could then only
include things that (if we could turn back time) we probably
would've liked to see in 'strict mode', but can't because that
ship sailed.
David Bruant set up a repo to collect these:
https://github.com/DavidBruant/ECMAScript-regrets
I don't think anyone wants to invest the time to create an actual
"spec" for ES5 \ "misfeatures", but collecting them and learning from
them is probably the next best thing.
Cheers,
Tom
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
