Re:Why Is Node Being Forked?
by tiagocesar on Thursday October 16, 2014 @01:24PM
(#8466095)
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.
Re:Why Is Node Being Forked?
by davidw on Thursday October 16, 2014 @03:15PM
(#8466905)
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.
Re:Why Is Node Being Forked?
by babby on Sunday October 19, 2014 @02:08AM
(#8477381)
Been using node in production at work for 6 months, and 2 years in general with zero immaturity issues. The only downside is userland modules which seem stable and active now days.
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.