4 ms·
Fortunately nowadays including any of those in your code would award you the review equivalent of bashing your head in. With the advent of linters most of thes
by Tade0 5y ago
Fortunately nowadays including any of those in your code would award you the review equivalent of bashing your head in.
With the advent of linters most of these patterns started being rightfully considered bad form by default.
Currently even innocent stuff like +new Date() (outputs a timestamp) is already something that I've rarely seen make it through review.
JS is goofy, but ES2015 managed to avoid making the same mistakes. Shame it took so long to implement it.
At the moment the bigger problem is the painful transition from whatever module system you had to ES Modules.
Especially browser<->Node.js interoperability suffered massively from this.
Hopefully there will be no further standards in this field.
- phist_mcgee 5y agoI am eternally surprised at how long it took node to support ESM. CommonJS modules served their purpose, but they are about to go the way of JS module systems. This is where the appeal of deno comes in. It's a runtime that tries very, very hard to give you the same API surface as that of the browser. I just hope deno catches on faster.
- Tade0 5y agoI consider Deno to be DOA - hopefully I'm wrong. The scope was just too broad.