The Artima Developer Community
Sponsored Link

Java Buzz Forum
Q&A: Why io.js decided to fork Node.js

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
News Manager

Posts: 47623
Nickname: newsman
Registered: Apr, 2003

News Manager is the force behind the news at Artima.com.
Q&A: Why io.js decided to fork Node.js Posted: Dec 4, 2014 8:25 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by News Manager.
Original Post: Q&A: Why io.js decided to fork Node.js
Feed Title: JavaWorld
Feed URL: http://www.javaworld.com/index.rss
Feed Description: JavaWorld.com: Fueling Innovation
Latest Java Buzz Posts
Latest Java Buzz Posts by News Manager
Latest Posts From JavaWorld

Advertisement

Node.js devotees who are dissatisfied with Joyent's control over the project are now backing their own fork of the server-side JavaScript variant, called io.js or iojs. To get the lowdown on what and who was behind this move, InfoWorld Editor at Large Paul Krill on Wednesday asked Mikeal Rogers, who has been involved with the fork and is director of evangelism at cloud hosting service vendor DigitalOcean, about the effort.

InfoWorld: Are you the person in charge of the fork?

To read this article in full or to leave a comment, please click here

Read: Q&A: Why io.js decided to fork Node.js

Topic: Java.util.EnumMap Example Previous Topic   Next Topic Topic: java.util.concurrent.Exchanger Example

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use