News for hackers. Stuff that matters.
Re:The state of JavaScript modules by camus2 on Monday May 29, 2017 @05:01AM (#14438173)
> After ~2016: "Stop improving JavaScript, I can't keep up!"

The bad parts are still here that's the problem. The language didn't improve so much that it got new features. But var, ==, type coercion and co still exist.

Re:The state of JavaScript modules by Vinnl on Monday May 29, 2017 @06:09AM (#14438371)
> But var, ==, type coercion and co still exist.

They all have alternatives, and linters can help restrict you to those alternatives. As a developer, that makes it pretty doable.

I presume you too can appreciate why they can't simply be removed.

Re:The state of JavaScript modules by aaron-lebo on Monday May 29, 2017 @05:17AM (#14438220)
So use a linter which disallows var and some of the worst usages and and use libraries which make up where it's lacking.

It's the price of improving the language + backwards compatibility.

Re:The state of JavaScript modules by camus2 on Monday May 29, 2017 @05:33AM (#14438266)
A linter never fixed the runtime behavior of a language, this is beside the point. The point is the assumption that Javascript is a better language today.
Re:The state of JavaScript modules by aaron-lebo on Monday May 29, 2017 @05:38AM (#14438281)
You mentioned var, let exists to fix those issues, hence the language just in that one area is better.
Re:The state of JavaScript modules by tlrobinson on Monday May 29, 2017 @06:29AM (#14438422)
The first two are totally solvable with a couple ESLint rules (`===` and `no-var`), and the latter somewhat solveable with TypeScript or Flow.