i don't agree that expressiveness is necessarily a good thing. expressiveness comes with a cognitive overhead when reading and thinking about code, it's in your head, always. the more feature, the more language semantics, the more you have to keep in your head before you even start adding the lines of code you're keeping in there.
saving 4 lines of code with new language semantics might save 4 lines, but those were 4 lines in one place that i only had to think about in that spot. the new expressiveness i have to carry around with me whenever i think about any code.
i don't think it's a win to add semantics to the language that accomplish something *we can already do*. there are lots of ES.next features that let us do something that we could not do at all previously (weak tables and refs are a good example). features that enable new kinds of applications we couldn't previous build.
i said it at NodeConf and I'll say it again here, nobody ever said "i couldn't write that app/feature because _javascript_ doesn't have classes".
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
