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 :)
[ Parent
| on HN ]
Or coroutines, like eventlet uses in Python. It's very readable, and asynchronous.
Another similar library: http://gevent.org
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.