News for hackers. Stuff that matters.
Re:Why node.js excites me by lzw on Monday September 27, 2010 @06:05PM (#1733667)
My concern about node.js is that it seems difficult to write server code that is readable later.... Since you're constantly creating handlers, it is kinda like programming the movie inception to me. Maybe a higher level abstraction on top might solve that.
Re:Why node.js excites me by dfox on Monday September 27, 2010 @06:08PM (#1733676)
That higher level abstraction is called "threads" and that is exactly what node.js tries to avoid :)
Re:Why node.js excites me by pjscott on Monday September 27, 2010 @08:53PM (#1734173)
Or coroutines, like eventlet uses in Python. It's very readable, and asynchronous.

http://eventlet.net/

Re:Why node.js excites me by denik on Tuesday September 28, 2010 @01:25AM (#1734676)
Another similar library: http://gevent.org
Re:Why node.js excites me by lzw on Tuesday September 28, 2010 @12:36AM (#1734578)
Processes (or threads) are not the problem, it is shared state / memory / side effects. Erlang has solved this pretty well, and I love the way it works, but do not find myself looking forward to the syntax.

Either choice means that the code is harder to read, but erlang is easier to read than node code, I suspect. (Will have to investigate.)

Re:Why node.js excites me by fauigerzigerk on Tuesday September 28, 2010 @03:37AM (#1734902)
You always have shared state somewhere. It makes no sense to me to force myself to have it exclusively in the database by choosing a platform that cannot do shared state or makes it extremely tedious. I agree with you on the handler maze though.
Re:Why node.js excites me by troygoode on Monday September 27, 2010 @06:59PM (#1733853)
I develop in - and enjoy - node, but that Inception metaphor is brilliant! You do get used to it though. :-)