Echo JS 0.11.0

Can confirm. I'm a web developer with 7 years commercial experience now. I don't have a single formal qualification or certificate.

I got into the industry by freelancing for small local businesses to build up a portfolio which I then used to get my foot in the door at a web agency as a full time developer, then just took it from there with that experience.

I like this, would make a good minimal alternative for building DOMs when using something like cycle.js

Doesn't https://www.npmjs.com/package/promisify already provide this functionality?

Interesting... is this an implementation/alternative of Promises?

Full size CMS isn't necessary, you could easily achieve all the needed functionality with markdown and git a la:

https://github.com/pyrokinetiq/Sails-Blog-Markdown

Yuck, it's running on WordPress?

I'd expect a site named js.org to be running JS itself. Why no nodejs, iojs or meteor?

Everyone seems to be exaggerating the likelihood of incompatibility, as far as I'm aware io.js is simply supposed to be a bleeding-edge version of node. There is no need for community library authors to test on or support io.js, because in theory io.js should be fully backwards-compatible with node.js other than the incredibly unlikely circumstance that io.js adopts a version of V8 which deprecates features used in node's version of V8 or changes it's API in a non-backwards compatible way, which would be no different from the incompatibilities you'd encounter by using a version of node to run an app written for an older version of node.

Forking node allows people to use new/experimental V8 features/improvements while still tapping in to the already massive node ecosystem and alleviates those users from having to compile their own node/V8 binaries. This way those working on personal/dev status projects can use the latest io.js to have the new features they might want, and those working on public/production projects can use the latest node.js without having to worry about instabilities.

To me node.js or io.js is analogous to choosing between an LTS/stable release or bleeding-edge/unstable release release of your OS. There's no universally correct choice, it depends on your specific requirements. Having both projects doesn't fragment the community, for example most Linux distro packages are compatible with both stable/unstable releases of the OS, the only exceptions being different versioned dependencies which is generally resolved automatically by your package manager anyway.