First "official" NodeJS build on Windows

Re:First "official" NodeJS build on Windows by wildmXranat on Wednesday July 20, 2011 @08:34AM (#2785168)

Just throwing it out there, but what is the real reason behind making it windows friendly? Do developers want it or is it done with intentions to make it more appealing for corporate absorption?

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by agnokapathetic on Wednesday July 20, 2011 @09:26AM (#2785373)

http://nodejs.org/nodeconf.pdf

With IO Completion Ports, the Windows kernel lends itself more to async server programming than Unix threads, Microsoft has committed to Joyent's port and with many developers working with Windows on their development boxes, even if they later deploy to a Linux environment, a windows port just makes sense.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by hkarthik on Wednesday July 20, 2011 @02:47PM (#2786919)

I shudder at the thought of writing Node apps in Windows only to later deploy them to a Linux environment. Sounds like a debugging nightmare.

Didn't we learn these lessons from the early days of Java when it was "write once, debug everywhere"?

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by bmj on Wednesday July 20, 2011 @10:03AM (#2785544)

I work at a Windows shop, and this comes at a good time for us, as node would scratch an itch, but prior to the Windows release, would have required additional infrastructure to use.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by andypants on Wednesday July 20, 2011 @08:44AM (#2785199)

Well... windows is a pretty popular operating system.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by noonat on Wednesday July 20, 2011 @09:26AM (#2785372)

There are definitely use cases. My last employer worked on browser based gaming, and we were forced onto Windows because most of the games we needed to support and work with only ran on Windows. I had a really hard tine getting any significant adoption of Node because running it on Windows was difficult.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by Strom on Wednesday July 20, 2011 @10:33AM (#2785698)

Node.js looks interesting and I may take a look at it. I would never install a different operating system just to try it out though.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by forgotAgain on Wednesday July 20, 2011 @12:29PM (#2786305)

Millions more developers can now play with it at work. Granted they could have been using a VM up to now but for many their machine can't handle a Java based IDE (Eclipse, Netbeans) within a VM.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by rbanffy on Wednesday July 20, 2011 @01:10PM (#2786508)

Millions of developers have been able to play with it since the first release - Node likely ran under Cygwin just fine from the start.

And you don't need VMs to run Java-based IDEs on Windows - there is a native JDK you can download from Oracle and Windows runs Eclipse and Netbeans acceptably.

[ Parent | on HN ]

Re:First "official" NodeJS build on Windows by MostAwesomeDude on Wednesday July 20, 2011 @12:58PM (#2786456)

The reason Twisted is available on Win32 is because (a) there are developers willing to test and maintain the OS-specific support for Win32, and (b) some people deploy apps which use Twisted as their general networking stack. (Deluge is one popular example of a Twisted-powered GUI app.)

I bet the former is the big reason; I don't think people write full user apps with GUIs in Node very often.

[ Parent | on HN ]