formula1
commented
9 years ago I appreciate the response, I hardly look at my old repos so I apologise about being late.
Competition would be nice though I'm aware that the node product is such a big plan with so few people capable and willing to maintain it. High demand product and low supply of solid devs. As a result, the separate project seems less than ideal.
There is certainly an element of hive mind. But I suppose since iojs will becoming part of node, it will likely get worse.
I doubt coorperate influence will do too much outside of influencing the direction of attention. Something like tls is extremely important to get right. So they'd likely be influencing iojs to handle tls rather than ensuring a good rasberry pi implementation
You are ON the spot!! There was a strong hive-mind mentality, and your comments were some of my favorite. I'm commenting here because the other thread is closed and I don't know how else to contact someone via github? I was on the exec board of frat for a few years, similar in size to this TC, and it's there's always personal shit happening behind the scenes, and it's private, and always portray a sense of unity, even in the worst of time.
To put this into perspective - our fraternity( with 100 members), when weed became banned, we had a stronger, more vocal, and higher % rate of participation compared to this merge.
TJ resigned which was also necessary. We're dealing with a new group of people we've never interacted with before and can't make judgement
But that's politics. Image a nodejs organization with lots of libraries. One library may be entitled iojs, another, nodejs. They may share code, they may disagree. Node might not want to upgrade v8, ever, iojs seems to really want that. There's a common ground.
Node.js is a library. io.js is a library. It's run off of v8, of which we have no little influence on, and JS, which is the language node.js chooses to use, it's not a language they build themselves. So we stand between the program and library API, with little influence on the language or runtime. Node is controlled by those processes first, the open source community / npm, core maintainers, and last but not least, the Committee. The committee has more influence on language features and compilers than we do alone, while also having least amount of influence 'here', on github. within the power structures
Regarding TC, corporate influences have the power of veto, which will throttle the current rate of io.js growth. Probably 10 fold. If io.js wasn't considered competition to node.js, merely a separate JS environment that is owned by the nodejs foundation and given the 'ok' by the TC to just carry on. In that scenario, iojs wouldn't threaten nodejs whatsoever, it would only increase the organizations popularity if they chose to do so. We could act like brothers living in the same house. The more children the merrier. The more nodejs / iojs become popular, more developers will want to contribute. Without the 'nodejs is the only way' attitude, why not chakra.js? As long as there's a continuity of developers, and org can make as many libs as they want, including node.js and iojs.