31–40 of 40 posts
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?
Unless you are deploying on Windows, why not run it under cygwin? You may end up with a lot of silly problems with file paths, case insensitivity and any other "impedance mismatch" between your development environment and whatever server the workload will run on. I did a lot of Django development on Windows and Cygwin saved me a whole lot of pain.
I just tried to install node on cygwin and it failed with this error: ------ src/uv-cygwin.c:33: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function) src/uv-cygwin.c:33: error: (Each undeclared identifier is reported only once src/uv-cygwin.c:33: error: for each function it appears in.) make[1]: * [src/uv-platform.o] Error 1
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?
I bet the former is the big reason; I don't think people write full user apps with GUIs in Node very often.
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?
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.
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.
Earlier quoted context omitted.
Does a javascript engine like V8 have to be installed separately to avoid dependency issues? Microsoft has the Chakra engine but as far as I know it was running inside IE only.
V8 is open source, so it's compiled into Node. But I don't even compile open-source libraries into my windows assemblies. That seems like an incredible waste of time for little benefit.
I think the benefit is huge and don't see how it's a waste of time. Node is linked to specific V8 versions, it makes sense to include it.
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?
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.
Didn't we learn these lessons from the early days of Java when it was "write once, debug everywhere"?
Earlier quoted context omitted.
V8 is open source, so it's compiled into Node. But I don't even compile open-source libraries into my windows assemblies. That seems like an incredible waste of time for little benefit.
The distribution & install story is better w/ a single statically linked exe (imo of course). Not to mention installing node for development and on servers. When everything is in one place it's just so easy. I think the benefit is huge and don't see how it's a waste of time. Node is linked to specific V8 versions, it makes sense to include it.
Earlier quoted context omitted.
I just tried to install node on cygwin and it failed with this error: ------ src/uv-cygwin.c:33: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function) src/uv-cygwin.c:33: error: (Each undeclared identifier is reported only once src/uv-cygwin.c:33: error: for each function it appears in.) make[1]: * [src/uv-platform.o] Error 1
It's been fixed in master. 0.5.2 comes out tomorrow (if all goes well) and will also contain the fix. https://github.com/joyent/libuv/issues/112 for details.