Built by John Resig. ES6 Overview in 350 Bullet Points. Apologies about that long table of contents, and here we go.
ES6 – also known as Harmony, es-next, ES2015 – is the latest finalized specification of the languageThe ES6 specification was finalized in June 2015, (hence ES2015)Future versions of the specification will follow the ES[YYYY] pattern, e.g ES2016 for ES7Yearly release schedule, features that don’t make the cut take the next trainSince ES6 pre-dates that decision, most of us still call it ES6Starting with ES2016 (ES7), we should start using the ES[YYYY] pattern to refer to newer versionsTop reason for naming scheme is to pressure browser vendors into quickly implementing newest features (back to table of contents) A new primitive type in ES6You can create your own symbols using var symbol = Symbol()You can add a description for debugging purposes, like Symbol()Symbols are immutable and unique. Time for a bullet point detox. Then again, I did warn you to read the article series instead. D3.js - Data-Driven Documents.
Meteor Tutorial. An Absolute Beginner's Guide to Node.js. There's no shortage of Node.js tutorials out there, but most of them cover specific use cases or topics that only apply when you've already got Node up and running.
In particular, a lot of people have complained that the semantics of this in function invocations is confusing. In my opinion, a lot of this confusion is cleared up by understanding the core function invocation primitive, and then looking at all other ways of invoking a function as sugar on top of that primitive. In fact, this is exactly how the ECMAScript spec thinks about it. In some areas, this post is a simplification of the spec, but the basic idea is the same. First, let's look at the core function invocation primitive, a Function's call method. Make an argument list (argList) out of parameters 1 through the end The first parameter is thisValue Invoke the function with this set to thisValue and the argList as its argument list.
It is designed mostly for compilers like Emscripten to target, but the best part is that it’s backwards compatible with the existing JS syntax since it is a strict subset. This means that asm.js code will still run on older browsers, although not in the optimized path taken in enhanced JS engines. You opt-in to using asm.js by including the "use asm"; string at the top of your file or individual function, just like you opt into strict mode with "use strict";. Once you’ve done that, the ahead-of-time (AOT) optimizing compiler will kick in in supported engines, looking for type annotations and validating the code to make sure it really is optimizable.