Installing and Running node.js applications within IIS on Windows - Are you mad?

I'm glad Node works on Windows - it'll make for more eyes on the code.<p>The "Why would I want node.js to run on Windows and IIS" bullets, if they're meant to compel you in the context of other platforms, I don't get:<p>* Process management - Upstart is standard in Ubuntu now and will manage your processes (respawn pragma).<p>* Scalability on multi-core servers - Nginx will load balance over as many or as few processes as you like with minimum configuration.<p>* Auto-update - great for development but count me out for production use. On unix needs a third-party app.<p>* Access to logs over HTTP - not sure why this is good? Anyway, easy win with Nginx.<p>The last time I tried to do any admin on Windows it was just an exercise in frustration. No decent shell (I've not used powershell - correct me if it's any good), clunky terminal, <i>awful</i> guis forced on the user and suppression of debugging information (including source code!).

Pretty cool. A lot nicer than running node.exe directly. I heard MS was working with Joyent to get Node running on Windows but I didn't think devs at MS would actually dedicate cycles to it and provide native IIS support. Awesome!<p>I played with node.exe a few weeks ago when it was first released and it worked well enough. The only problem was the lack of Windows-compatible packages. Most assume you're on *nix. Node without NPM is handicapped.

Is there any question any longer that MS is a second class web platform?

This is of limited use at the moment. Most of the useful node packages assume a unix system