If these projects don't get merged, it's going to be a shitshow in my opinion.
[deleted]
Io.js and Node.js reconciliation proposal
31–40 of 83 posts
Re: Io.js and Node.js reconciliation proposal
#32I really hope we can see a unification of the efforts and work through the political issues. Having very talented developers working on separate codebases instead of improving one seems counterproductive.
They have to merge otherwise one will die. There is no alternative. I hope it happens sooner rather than later.
[deleted]
Re: Io.js and Node.js reconciliation proposal
#33Why reconcile? This is awesome competition. It involves open-source competitors. Today's gripes will soon be forgotten.
Re: Io.js and Node.js reconciliation proposal
#34What's the background to all this? I'm not a JS dev so haven't been following, but the history would be interesting.
Re: Io.js and Node.js reconciliation proposal
#35Earlier quoted context omitted.
Well, considering the issue was created 6 minutes before you posted this comment, this is facetious and disingenuous.
Given that the Node guys are publicly saying things like 'Io.js, what's that?' I think a little bit of snark is justified.
Wow. Can you provide a URL?
Re: Io.js and Node.js reconciliation proposal
#36What's the background to all this? I'm not a JS dev so haven't been following, but the history would be interesting.
OK, so: Henry VIII needed a male heir to ensure his power on the throne...
Re: Io.js and Node.js reconciliation proposal
#37Why reconcile? This is awesome competition. It involves open-source competitors. Today's gripes will soon be forgotten.
it's open source, not commercial. there's no point for competition. it's better to join resources and create equilibrium. the industry will need standards which will cause one project to die (sooner or later) and we will loose all the talent and energy spent there.
Re: Io.js and Node.js reconciliation proposal
#38Earlier quoted context omitted.
Given that the Node guys are publicly saying things like 'Io.js, what's that?' I think a little bit of snark is justified.
Wow. Can you provide a URL?
>> “IO.js, what’s that?” asked Joyent CEO Scott Hammond in response to my query about whether projects based on the fork would be able to enter.
http://readwrite.com/2015/02/03/joyent-nodejs-incubator-iojs...
Edit: Agreed with @caipre's reply that the quote isn't as bad as it sounds totally out of context (in hindsight I should have included more of the context in my reply too), and was probably meant tongue-in-cheek. However, I think considering the (perceived? real?) animosity between these two projects, his choice of wording could have been better.
Re: Io.js and Node.js reconciliation proposal
#39Why reconcile? This is awesome competition. It involves open-source competitors. Today's gripes will soon be forgotten.
it's open source, not commercial. there's no point for competition. it's better to join resources and create equilibrium. the industry will need standards which will cause one project to die (sooner or later) and we will loose all the talent and energy spent there.
Competitive pressure isn't just useful for commercial projects, it is also useful for open source projects.
Re: Io.js and Node.js reconciliation proposal
#40Why reconcile? This is awesome competition. It involves open-source competitors. Today's gripes will soon be forgotten.
it's open source, not commercial. there's no point for competition. it's better to join resources and create equilibrium. the industry will need standards which will cause one project to die (sooner or later) and we will loose all the talent and energy spent there.
The joint resources/equilibrium broke down. That’s why the fork happened. It's a natural process.
Open-source competition is critical and beautiful. This is a major function of Github and a big reason why it’s successful.
Forget what the industry needs. Technology creates the industry. Now we're at the crossroads between the next great tech and the next great bureaucracy. Which side sounds cooler?