JavaScript Roundup (November 2014)

• James Long has concerns over ES7 async/await. You can use it today in 6to5 and traceur.
• Mach – “An HTTP server and client library that runs in both node.js and the browser.” My question: Why not use the more mature express? Michael’s answer: “mach is like express, request, node-http-proxy rolled into one, with a little nginx and Apache sprinkled in as well, with a thoughtful API.”
• Isomorphic Flux, by Michael Ridgeway. This made a big splash. Whether it actually becomes a thing remains to be seen.
• React.js Conf, EmberConf, ng-conf. Terran, Zerg, Protoss.
• IE team announces support for more ES6 language features. They are kicking butt.
• avik in freenode#flowtype summarizes Flow’s main difference from TypeScript: “The main difference is that flow treats missing annotations as omitted static types (to be inferred) whereas typescript treats them as dynamic by default. as such, flow potentially catches many more errors than typescript for equivalent effort.”
• A good discussion on the differences between Flow’s and TypeScript’s type systems
• 6to5/issue-95 – Great JS minds discuss making ES6 module format transpilation work better with existing CJS
• Async Generators – Composable Async Programming in ES7. Now I feel dumb.
• Regulex – JavaScript Regular Expression Visualizer
• Oldie: Learning JavaScript Design Patterns

Concerns with GSS:

@jlongster That's to say: the new awesomeness of JS virtual DOM implementations is incompatible with this new awesome CSS implementation.

— Philip (@wwwphilcom) November 15, 2014

async/await is sugar for something like co

Updated prediction: There will be exactly 1 people in the world who use JS generators after async/await ships

— JeffMo (@lbljeffmo) November 12, 2014

Fightin’ words:

.@trek I'm convinced that we CommonJS people need to declare war on alt. formats until AMD et al unilaterally lay down their arms

— Pete Hunt (@floydophone) November 12, 2014

Concern over node’s technical debt grows:

TIL: every production system running on Node is using an unsupported version of v8 w/no possibility of bug fixes: https://t.co/DFbQxITHYz

— λ nerd (@briancavalier) November 12, 2014

Advantage of using JWT:

@domenic @dschenkelman the idea is that in case of CSRF Cookie header is set automatically and Authorization is not. ExtendWebFwd & all that

— Андрей Листочкин (@listochkin) November 17, 2014

React leads the way:

hmm, #polymer changed its 2-way data binding to be opt-in… #chromedevsummit @reactjs

— Pete Hunt (@floydophone) November 19, 2014