Slashdot Mirror

And if you are really claiming that packages here https://www.npmjs.org/browse/d... are not stable and dependable, you sir are an idiot.
Same with this http://stats.bower.io/

https://www.npmjs.org/

Rx isn't really the same as callbacks, otherwise you wouldn't need this. And if you object to the terminology, blame Microsoft.

Anecdotally (having worked with node.js for the past year or so), whenever I've needed to do something not available in the core libraries, there has been an npm for it, usually several. But - and this is a rather big but - their maturity can vary quite a bit. The biggest issue really is documentation, that can be incorrect or completely out of date. Yes, there always is the source, but that's hardly ideal.

Having said that, in general I do like node.js. It takes some time getting used to and you have grasp Javascript well in order to use it efficiently, but if you're working with JSON data (we use CouchDB) it's quite a natural fit.

Yes, I've heard that LuaJIT might be faster than Node.JS, though I haven't seen any definitive benchmarks. If true, it won't be a huge order-of-magnitude difference as it is compared to Ruby.

Seems that the Node Package Manager has a large collection of modules already, and is growing very quickly. JavaScript itself is vastly more popular than Ruby or Lua, so it makes sense that its leading server-side implementation would get a lot of attention from module developers in the near future. (And the popularity of JS is usually greatly underrated, because people don't call it by a consistent name when talking about "Web scripting", "AJAX", "EcmaScript", "SSJS", "Node", "JScript", "Apple Dashboard Widgets", "Firefox add-ons", "Google Apps Script", etc.) Node.JS is still inching toward that 1.0 version, which would send a signal to a lot of people that it's ready for serious use.

I'm not here to make any "point" against Ruby, just to present my current opinion and ask why people choose Ruby over the alternatives, particularly Node.JS.

--libman

I suggest diving into Node. It is written in a very competent way, it's fast, small, efficient, nicely documented, does the IO correctly so no messy blocking function calls and threads synchronization madness, and is pretty young so the code base is not too big for one person to understand. Thanks to npm it is also very easy to write modules that are small, clean and have minimum boilerplate code so it's not like writing Java. There is a lot of code to be written so you may find writing and publishing your own useful modules pretty soon. Good luck!