Installing and Running node.js applications within IIS on Windows - Are you mad?
hanselman.com
hanselman.com
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:
* Process management - Upstart is standard in Ubuntu now and will manage your processes (respawn pragma).
* Scalability on multi-core servers - Nginx will load balance over as many or as few processes as you like with minimum configuration.
* Auto-update - great for development but count me out for production use. On unix needs a third-party app.
* Access to logs over HTTP - not sure why this is good? Anyway, easy win with Nginx.
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, awful guis forced on the user and suppression of debugging information (including source code!).
* usable for the task at hand
* inferior to similar tools that are 20 years old
* slower / more resource hungry than it should be
I'm guessing/hoping it has something to do with native HTML5 apps + javascript + windows hooks for native "Touch first" apps coming in Win8.
Add that to native Kinect support on Win8, and you have a pretty kick ass gesture / touch based UI on a PC.
We'll find out more at BUILD in 2 weeks.
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.
The way Stackoverflow operates (leveraging developer platform expertise + commercial and opensource tools) should be seen a role model. Unfortunately, in Microsoft circles, it's more of a black sheep.
Glad to hear that Joynet is porting Node to windows. Now lets get npm to Windows.
Node is like the wild west 1800s so come prepared.