I predict that 0.10.x will be with us for a long time. It's now the Windows XP SP2 of Node.js releases. It'll be interesting to see how long it takes before Joy

I predict that 0.10.x will be with us for a long time. It's now the Windows XP SP2 of Node.js releases. It'll be interesting to see how long it takes before Joyent refuses to accept patches to the 0.10.x branch. When they do, that'll be the point to seriously consider moving off of Node.js to a project with adults running it. In addition to all of the political crap with Joyent, the changes in 0.12.x are incredibly onerous at the C++ level, for no obvious benefit whatsoever (thanks, v8 team). I know our company is sticking with 0.10.x for the indefinite future because we're not allocating man power to update the dozen or so compiled node modules we use (along with all of the new bugs changing that many changes will inevitably bring with it). Instead, in the future we'll be dropping down to either libuv directly (all of our compiled libraries are written in C–C++ is just used to bind to Node.js), and we're also looking carefully at luvit, since Lua binds to C so nicely, and LuaJIT is seriously awesome. :) So between Joyent forcing Ben Noordhuis out and their corporate "it's our way or the highway" bullshit, we just have a really bad taste in our mouths about the future of Node.js with Joyent at the helm.