{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Melony? 的问题《Is Node.js production-ready on Windows? [closed]》','https://www.manongdao.com/q-1022570.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
In the new 0.5.1 branch, there is an official Windows executable of Node.js. The Linux version of Node.js uses established libraries such as v8, libev, libeio.
Since libev and libeio is for *NIX platforms; is the Windows port of Node.js ready for production use, or is it only for development?
I have tried the Windows version of Node.js (0.5.1). It actually works very well, but I couldn't load "child_process" module. It seems that it was not shipped with the current version.
Just my two cents.
Updated: Here is the TODO.Win32, which answers my questions.
0.5.x branch is unstable. Even branch numbers are stable and odds are unstable, so you will have to wait for the 0.6.x if you want it production ready and stable.
Version 0.5.1 is marked unstable, so don't expect this to be production quality. Microsoft seems to back the Win32 port of Node however, so in the (near?) future it will be stable.