I hope it's well optimized for fibonacci algorithms now.
Not to worry! Until we can get the desperately needed native Fibonacci support (lest the haters hate), there is always node-fib: http://news.ycombinator.com/item?id=3067403
Node.js v0.6.0 is released
31–38 of 38 posts
Re: Node.js v0.6.0 is released
#32Next for windows developers is trying to get npm to work. The sheer popularity of unix tooling in the build process means that using node libraries is likely to remain a challenge.
While it's true that a lot of Node libraries assume *nix and make system calls, a surprising number of libraries are written in pure Node. Just clone the library from GitHub and put it in the node_modules directory and you're good to go for a number of popular libraries. I've played around with Node in Windows and Node without NPM is seriously gimped.
Well, ryppi.py is a python script which works like npm. Once you are done with it you can install any of the libraries by using the following command.
python ryppi.py install socket.io expressRe: Node.js v0.6.0 is released
#33Node Cluster? http://nodejs.org/docs/latest/api/cluster.html
Is it me or does this look like the early makings of an erlangish otp, eh?
Re: Node.js v0.6.0 is released
#34Am I the only one that thinks that Windows support was not really worth the time? Sure, you get to support a huge chunk of the OS market, but what are the real implications of Node running natively on Windows?
Microsoft funded the work. My guess is since they're pushing for JS client-side apps now with WinRT; they funded node on Windows so that JS developers can run their server-side code on Windows instead of being tempted to fire up a *nix server instead. (AFAIK, MS doesn't have any server-side JS tooling similar to node at the moment. Very good chance that I'm wrong, though.)
Microsoft has JScript.NET (and has for a while now).
http://msdn.microsoft.com/en-us/library/ms974588.aspx
I haven't seen it used anywhere as a server side application, though.
Re: Node.js v0.6.0 is released
#35Am I the only one that thinks that Windows support was not really worth the time? Sure, you get to support a huge chunk of the OS market, but what are the real implications of Node running natively on Windows?
Wow.. yeah, who would want Node on Windows? Whats the point. LOL. The sad thing is, that is probably the default perspective. Basically what's going on is status quo bias -- its the same thing with dying. There's nothing you can do about it so you learned to accept and love that Node.JS doesn't work on Windows. Who would want to live forever? Dying is great! Or you just don't want to have anything to do with Windows or something. People are amazingly stupid. I'm sorry, but its just stupidity to react that way.
"Sure, you get to support a huge chunk of the OS market" 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.
Re: Node.js v0.6.0 is released
#36Earlier quoted context omitted.
Microsoft funded the work. My guess is since they're pushing for JS client-side apps now with WinRT; they funded node on Windows so that JS developers can run their server-side code on Windows instead of being tempted to fire up a *nix server instead. (AFAIK, MS doesn't have any server-side JS tooling similar to node at the moment. Very good chance that I'm wrong, though.)
Microsoft has JScript.NET (and has for a while now). http://msdn.microsoft.com/en-us/library/ms974588.aspx I haven't seen it used anywhere as a server side application, though.
JScript.NET was dropped for .NET 4.0; it has always been a bit of a curiosity though. I think it was there because "classic" ASP had support for doing server-side scripting in JScript, so somebody thought ASP.NET needed to support it also. Thankfully, there are a few alternative JavaScript implementations on .NET such as IronJS.
Re: Node.js v0.6.0 is released
#37Earlier quoted context omitted.
Any numbers for node on ARM? I was told that recently v8 releases have had significant performance regressions for ARM devices by a JS dev at a meetup.
Can you give more information about this? 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. Thanks.
[deleted]
Re: Node.js v0.6.0 is released
#38Wouldn't run node on windows in production, but it makes it a heck of alot easier for dev work.