SebastianVerified account

@trek @searls I thought it was a stability thing with Node not being up to date on V8.

@justinbkay @searls and you don’t need to be part of some OSS cabal to know it. Literally every article says “fork” http://readwrite.com/2014/12/08/node-js-fork-io-js-isaac-schlueter-statement …

@trek yup thanks for the added perspective. I am not yet convinced that they won't coexist and that people won't view them as alt impls

@trek where by "alt impl" I mean "a thing to be chosen and viewed as kind of sort of interchangeable"

@trek at least that's how I think average folks will view it until a preponderance of npm modules only work with one

@searls I suspect packages will begin using ES6 features quickly (https://iojs.org/es6.html ) and node will be the IE6 of server javascript

@trek @searls I plan on republishing with 6to5 so stuff still works

@jergason @searls ugh. Paging @seldo. This is an example of why npm could really use a notion of multi-format publishing.