Edit: Seems like it's a regression that will likely be fixed for 0.6.1.
(AFAIK, MS doesn't have any server-side JS tooling similar to node at the moment. Very good chance that I'm wrong, though.)
I haven't seen it used anywhere as a server side application, though.
"Sure, you get to support a huge chunk of the OS market" <-- This is a big deal.
Most businesses run Windows. I want my Node.JS software to run on most business servers or workstations without requiring a VM or something. Same with most PCs.
The implication is that I can provide Node.JS-based software to an additional 400 million or so people. That means that I can write my software for Node.JS and not have to write a different version for Windows or ignore 400 million people.
For example, say I built an online database application builder type thing where users can build forms using drag and drop and configure database search screens and reports easily. What a lot of my users really want is to have complete control over their database and application. They don't want to have to rely on my server or their internet connection always being on to access their business data.
With good Windows support, I can build my application in Node.JS, and provide a setup bundle that users or IT people can use to install the user's database application on a Windows server.
Seems pretty obvious that this is a big advantage.
Not that that's a bad thing at all, but it would explain the seemingly unusual choice.
When Microsoft SQL Server, Exchange and Sharepoint run on on Linux we will know that has change happened.
"Integrated load balancing over multiple processes."
These two improvements are just the nudge I needed to start tinkering with Node. I've been following along and reading about node almost daily but native windows support and integrated focus on multiple processes make a big difference to me. I can no longer sit on the sidelines.
Thanks for picking me up and shoving me onto the field!
Question: Since this doesn't look that complex, is anyone working on an automagical translator from 0.4 to 0.6 that people could use?
I've played around with Node in Windows and Node without NPM is seriously gimped.
python ryppi.py install socket.io express
Note that I/O read performance is up 35%, from 19.7 mb/s in 0.4 to 26.6 mb/s in 0.6.
If you know that JS dev personally please ask him to file the bug (http://code.google.com/p/v8/issues/entry) or send any information he has about regressions to v8-users mailing list.
I don't think there were any bugs opened recently about perf regressions on ARM devices.
Keep up the great work, btw! I'm pretty excited to move up to Node 0.6 (probably-statistically-insignificant regression on IO-write regardless)!
Is it me or does this look like the early makings of an erlangish otp, eh?