mf - story #5985

MOAR JS
posted by dsk on November 9th, 2011 at 3:03PM

http://www.ibm.com/develo...odejs/index.html

What's wrong with Node.js?

"Node's stated number one goal is 'to provide an easy way to build scalable network programs'. What's the issue with current server programs? Let's do the math. In languages like Java and PHP, each connection spawns a new thread that potentially has an accompanying 2 MB of memory with it. On a system that has 8 GB of RAM, that puts the theoretical maximum number of concurrent connections at about 4,000 users...Node solves this issue by changing how a connection is made to the server. Instead of spawning a new OS thread for each connection (and allocating the accompanying memory with it), each connection fires an event run within the Node engine's process.... So now that you have a program that can handle tens of thousands of concurrent connections, what can you actually build with Node?"

"Node itself runs V8 JavaScript. Wait...what?"

Link

posted by dsk on November 9th, 2011 at 4:54PM

Bow to your Javascript God.

Link

posted by dennisn on November 9th, 2011 at 10:06PM

So what? This doesn't address any of the very serious problems I have with JavaShit -- which are mainly client-side -- namely that it (my implementation) consumes absurd amounts of CPU to render bloody text/images, that it ruins the parseability/semantics of webpages, that it introduces all kinds of security holes, not only directly via unaccountable centralization of the code, but indirectly via unecessarily open doors and bugs.

In terms of this off-topic server-side stuff, I've been using lighttpd for a long time now -- you sure it doesn't do the same stuff, perhaps even better? I don't see anything unique with "Node" that can't be accomplished by any of the other competitors, via a module or patch or something. (It's not that hard to queue i/o, or to lower thread footprints). And, it seems to me like this has nothing to do with JavaShit, but rather with this "V8" thing -- ie. it's V8 that seems to have the more efficient resource usage? But probably not any of the other JavaShit implementations? So you probably meant "moar v8".

Link

posted by dsk on November 10th, 2011 at 9:54PM

> This doesn't address any of the very serious problems I have with JavaShit -- which are mainly client-side

Actually .. I have no clue what your problem with Javascript is. I'm trying to figure out if you have a problem with the language itself (i.e. the syntax), or if you just hate the idea of any dynamic language (e.g. Python) executing client-side.

>V8 that seems to have the more efficient resource usage?

V8 is a javascript engine. It executes Javascript code "by compiling JavaScript to native machine code before executing it, rather than to execute bytecode or interpreting it" - essentially hitting native speed. It just so happens to be the exact same engine that Google Chrome runs client-side to execute client-side code.

Link

posted by dennisn on November 11th, 2011 at 7:10AM

No clue? I just concisely listed five huge reasons -- and there are others. I don't really care about syntax/language, nor do I have anything against interpreted languages in general -- I use Bash and PHP all the time.

Link