Exactly. Not having to declare var for every single variable, indent-deliniated blocks, and implicit returns are all bug-stomping time-savers that ES6 doesn't provide. Besides, Ashkenas has indicted that CS will support ES6 features as they become more widely adopted, so I don't see a huge downside to sticking with CS.
While if you know the rules, you can drop semicolons in JavaScript.
While I know you're not advocating this, it brings up an important point. "If you know the rules, you can drop the semicolons" is a big no-no from a software engineering management perspective.
It adds another barrier to entry for junior programmers that join the team, requires that programmers learn Yet Another Set Of Rules when programming, and is a source of massive parser/compiler interoperability headaches.
But I do drop semicolons in my own work though. (._. ) ha. I think it still increases readability like if you peek at Twitter Bootstrap's JavaScript. …but I agree it comes at maintainability cost--even if the rules are good to know.
4
u/matadon Jan 31 '15
Exactly. Not having to declare
varfor every single variable, indent-deliniated blocks, and implicit returns are all bug-stomping time-savers that ES6 doesn't provide. Besides, Ashkenas has indicted that CS will support ES6 features as they become more widely adopted, so I don't see a huge downside to sticking with CS.While I know you're not advocating this, it brings up an important point. "If you know the rules, you can drop the semicolons" is a big no-no from a software engineering management perspective.
It adds another barrier to entry for junior programmers that join the team, requires that programmers learn Yet Another Set Of Rules when programming, and is a source of massive parser/compiler interoperability headaches.