4 ms·
Because no engine implements the whole recent standard and does everything in a 100% standard-conformant way. Learning an imaginary language seems impractical.
by qwerty456127 7y ago
Because no engine implements the whole recent standard and does everything in a 100% standard-conformant way. Learning an imaginary language seems impractical. I feel more sympathetic to Mozilla than Google but from the practical point of view, again, choosing the Google version for the reference makes more sense as it has more browser market coverage + Node. I've also made a game in vanilla JS recently (using only the Mozilla website for the language and APIs reference) and it works smooth in Chrome but glitches in Firefox.
- brlewis 7y agoOne advantage of using browsers when you want "modern JavaScript (as supported by the most recent version of V8)" is that the fetch API provides a great opportunity to try out async/await, which is the most new language construct. You'll pick up destructuring assignment and optional chaining in minutes, but async/await will make you a better programmer in other languages too, once you get some practice with it. If you're dead set against browsers, you'll probably have to use deno since its API is friendlier to async/await than node's is.
- qwerty456127 7y agoI'm not set against browsers at all. But I didn't know V8 had any problems with async/await. Tank you for highlighting this.