Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Io.js and Node.js reconciliation proposal

github.com

Post reply on HN
Print view View original

71–80 of 83 posts

Re: Io.js and Node.js reconciliation proposal

#71

Post by izolate »

jsprogrammer wrote: post #53
fapjacks wrote: post #42

Oh man I love it! There's no way Joyent is going to say yes to this, and the best part is that these are absolutely reasonable, sensible proposals. I grok that io.js core devs are totally serious about merging back into Node, but there's no way Joyent is going to go for this. I expect at best a counter-proposal (that may not even be public) that doesn't do these points justice. The ball is absolutely in Joyent's cour…

Why do you think Joyent will not say yes?

Because in doing so they relinquish complete control in favor of io.js interests. I'm rooting for io.js, but this proposal amounts to what is essentially a takeover, not a merge.

Re: Io.js and Node.js reconciliation proposal

#73

Post by dagw »

jsprogrammer wrote: post #53
fapjacks wrote: post #42

Oh man I love it! There's no way Joyent is going to say yes to this, and the best part is that these are absolutely reasonable, sensible proposals. I grok that io.js core devs are totally serious about merging back into Node, but there's no way Joyent is going to go for this. I expect at best a counter-proposal (that may not even be public) that doesn't do these points justice. The ball is absolutely in Joyent's cour…

Why do you think Joyent will not say yes?

Because 'owning' Node is one of Joyent's big unique selling points.

Re: Io.js and Node.js reconciliation proposal

#74

Post by uptownJimmy »

fapjacks wrote: post #42

Oh man I love it! There's no way Joyent is going to say yes to this, and the best part is that these are absolutely reasonable, sensible proposals. I grok that io.js core devs are totally serious about merging back into Node, but there's no way Joyent is going to go for this. I expect at best a counter-proposal (that may not even be public) that doesn't do these points justice. The ball is absolutely in Joyent's cour…

What is there to love, precisely?

I must admit, I had some weird notion when I first started programming that the world of software geeks might be just a little bit less drama-centric than the rest of the human world, but I was very wrong. The soap-operatic emotions around Node are amazing to me. Good lord, it's JavaScript on the server, not royal palace intrigue...

Re: Io.js and Node.js reconciliation proposal

#75

Post by keslag »

inglor wrote: post #23
simlevesque wrote: post #21

Earlier quoted context omitted.

Just because no one has had the time to read the whole thing, think deeply about his position and state it in the last hour proves nothing.

Ok. Here are some issues from joyent/node that have not gotten any comments in over a month: https://github.com/joyent/node/issues/9022 https://github.com/joyent/node/issues/8987 https://github.com/joyent/node/issues/8975 https://github.com/joyent/node/issues/8974 https://github.com/joyent/node/issues/8931 Just randomly went to the issues page and looked

Try filling an issue with Google or Apple some time. If you think a month is a long time to wait for a response, you're going to have a bad time.

Re: Io.js and Node.js reconciliation proposal

#76

Post by serve_yay »

uptownJimmy wrote: post #74
fapjacks wrote: post #42

Oh man I love it! There's no way Joyent is going to say yes to this, and the best part is that these are absolutely reasonable, sensible proposals. I grok that io.js core devs are totally serious about merging back into Node, but there's no way Joyent is going to go for this. I expect at best a counter-proposal (that may not even be public) that doesn't do these points justice. The ball is absolutely in Joyent's cour…

What is there to love, precisely? I must admit, I had some weird notion when I first started programming that the world of software geeks might be just a little bit less drama-centric than the rest of the human world, but I was very wrong. The soap-operatic emotions around Node are amazing to me. Good lord, it's JavaScript on the server, not royal palace intrigue...

Yes, software development involves humans, like many other human endeavors.

Re: Io.js and Node.js reconciliation proposal

#77

Post by runewell »

I hope the two groups are able to work out their differences. I would love to see some of the strengths of io.js transfer into Node.js from both a technical and organizational perspective. The io.js project has been surprisingly thorough. So far they have kept on a consistent schedule of updates, provided excellent transparency regarding their team meetings and working groups, and they have been very responsive to feedback. I still use Node.js (with the harmony flag) for my production servers in hopes that there will be a merger soon but I may be in a dilemma if it doesn't happen within the next few months.

Re: Io.js and Node.js reconciliation proposal

#78

Post by mh- »

mintplant wrote: post #54
petercooper wrote: post #46

Earlier quoted context omitted.

Such a coup does rest on most of the 359 working groups voting in agreeance according to the provisional and not yet entirely decided, declared, or ratified by-laws of the tentative constitution of the current committee's purview of the project, however. My opinion? I shall say that, as far as we can see, looking at it by and large, taking one thing with another in terms of the average of the will of the working grou…

Downvoted or not, this is now my favorite comment on the site. Bureaucratic surrealism is the best way to describe the situation.

I can't believe I read it to the end. After, I googled some of the text to see if this was a variant of some copypasta.

Re: Io.js and Node.js reconciliation proposal

#79

Post by ac360 »

spronkey wrote: post #70
ac360 wrote: post #61

Earlier quoted context omitted.

The path is technical, the goal is technical. Teams are involved so both are also political. Most importantly, we should not spend any more of our precious time on this unnecessary distinction. Change is the only certainty. As a javascript developer I now have two options to help me through those changes. That makes me happy. Lastly, I love a good fight.

Well, not quite. Instead of one good option you now have two less good ones. Not exactly a win.

io.js is moving along swiftly and its mere existence has already inspired Node.js to be better.

It's a huge win already and will continue to be.

Re: Io.js and Node.js reconciliation proposal

#80

Post by tracker1 »

stingraycharles wrote: post #45
morgante wrote: post #43

Honestly, this just makes io.js look even more childish. They're issuing ultimatums without any reasonable chance of success. There are completely logical technical reasons for forking node into io.js. There are even political changes which need to be made. But instead of trying to reasonably discuss the future of Node in a collaborative fashion, io.js has essentially issued an ultimatum which determines the entire g…

Yeah this whole issue can even be interpreted as being passive-agressive. Not saying that it is, but it just has a weird feeling surrounding it, almost as if there is a huge grudge between each other, and being overly political (correct). They are not really starting a discussion, this is more of a "you need to do everything different, or else..", as if they are now building up some evidence that they can later use t…

Given that the majority of development contributers went over to io.js, it makes sense for the structure for technical decisions to more closely resemble io.js while yeilding marketting type things to the new Node.js organization.
Post reply on HN