11–20 of 20 posts
Earlier quoted context omitted.
It's just an expression, he stepped down: http://blog.nodejs.org/2014/01/15/the-next-phase-of-node-js/
If it's just an expression than maybe "forking" is also just an expression with a random meaning? Either that or he never was a BDFL.
Mikeal's response: " @ddtrejo @izs @piscisaureus it’s a fork as in the GitHub fork button sense." https://mobile.twitter.com/mikeal/status/520285400279965698 This article acts as if they are going their own separate ways when this is clearly not the case. Why did someone make a fork? Maybe to submit a patch? Maybe to have their own copy in case the origin decides to delete? Please be accurate in your posts. Misreport…
- https://github.com/node-forward is an organisation, not an individual and has put up various repositories centering around the forking effort.
- They have set up a website, http://nodeforward.org/ - which indicates (albeit with scant detail/background) that this is an independent effort to improve node.
- as zzmp pointed out, there is a fair bit of discussion around indicating some political discontent: https://github.com/node-forward/discussions/issues/7
https://mail.mozilla.org/pipermail/es-discuss/2012-October/0...
Maybe Node will finally get a free operator now: https://mail.mozilla.org/pipermail/es-discuss/2012-October/0...
It's kinda exciting for devs to use something that's actually still being built, but now we'll face different versions of the same tool. And, taking in consideration the oficial NodeJS will still be the one owned by the current BDFL, I fear this split of ideas actually inject problems for developers getting introduced to node.
Now I start to understand a coleague who don't recommend using Node before it gets mature. It's kinda exciting for devs to use something that's actually still being built, but now we'll face different versions of the same tool. And, taking in consideration the oficial NodeJS will still be the one owned by the current BDFL, I fear this split of ideas actually inject problems for developers getting introduced to node.
Now I start to understand a coleague who don't recommend using Node before it gets mature. It's kinda exciting for devs to use something that's actually still being built, but now we'll face different versions of the same tool. And, taking in consideration the oficial NodeJS will still be the one owned by the current BDFL, I fear this split of ideas actually inject problems for developers getting introduced to node.
I took a very brief look at node for a recent project, but decided that Erlang was way more mature and stable, albeit less trendy and with fewer libraries for it.