Slides from my talk about the nodejs fork "iojs" at the Munich Nodejs User Group meetup.
The Walking Dead NodeMunich Node.js Meetup #17, December 4
View Slide
Node is deadLong live IO?Issue #37
First Contact
GitHub
Twitter@KenanSulayman it's just a fork. don't worry. if it gets relevant, we'll all gonna know :D— Julian Gruber (@juliangruber) 30. November 2014
Reaction
Second Contact
Twitter Ibrb, migrating everything to io.js: https://t.co/fgQk49HqAW— Jan Lehnardt (@janl) 3. Dezember 2014
Twitter IIThis year I am thankful for https://t.co/HCzm02Zu8M 🙌#— Jongleberry (@jongleberry) 27. November 2014
Twitter III#iojs-Tweets
Background
ProblemsDelay in new releasesCore contributors leftJoyent forced policy
Future
ScenariosIO.js replaces Node.jsNode.js and IO.js coexistJoyent gives IO organization name rightsWait until end of Januar
Plans6-Week release cycleQuick V8 update adoptionOpen Governance ModelAddon-layer (like nan)Split node in submodules (libuv.js, stdlib.js)Clean up stdlib (e.g. deprecate domain)
Impact
For DevelopersLearn a new command.find . ‐name "*.js" ‐exec sed ‐i "" "s/node/iojs/g" '{}' \;
For RecruitersRecruiter looking for #iojs developers, 4 years experience required #nodejs— Lloyd Watkin (@lloydwatkin) 3. Dezember 2014
Final Words
SourcesGithubLogo DiscussionsRelease DiscussionsEran Hammer (Walmart)More Background Information
Thank YouFollow me on twitter @bodojs and on github bodokaiser or write me an email [email protected]