Very Nice post!!

I would just add the emphasis that fibers or streamline are not just
about esthetics against the "callback pyramid of doom", but without
having to code something a little more complex, you end up writing
state machines - at least I do. While correct state machines are
pretty efficient little devils, we humans do not well with 'em - at
least I do. Neither in coding nor debugging. And the more complex a
state machine gets, the worse it becomes. Thats why I prefer, if there
is a statemachine, to have it been generated by e.g. streamline, which
gives me the impression in coding and debugging, I deal with process
flows, which the normal human brain working better with - at least I
do.

On another aspect, while there is much potential in TAGG, right now I
don't quite seem the difference to true inter process communication
(IPC). Yes on windows, a thread is cheaper than a process, and their
IPC-pipes aren't as efficient as on Linux (at least i heared), but
thats soley a windows kernel phenomenon. I agree, once we get shared
immutable states (which can switch the whole tree atomicly) then
threads start to develop their true power.

Finally, i wonder, when delving into this systems, if we will hit the
barriers of Javascript soon enough, or if it can be made adaptable.
Otherwise there might be a point where it is benefetical to switch to
a language thats build with immutables from start (like Clojure). I'm
still playing with my mind writing a meta (preprocessor) language,
which has (almost) everything immutable by default and compiles itself
to javascript, so it runs in the browser as well in node. Suppose the
idea will stay cloudy for a while, until it might make sense. If
anyone would want to join a drafting process like that, we could start
making a wiki or so.

- Axel

On Sun, Mar 11, 2012 at 9:42 PM, Bruno Jouhier <[email protected]> wrote:
> Since this week node has both threads and fibers. Fibers have been available
> for more than a year (https://github.com/laverdet/node-fibers) and threads
> landed this week with Jorge's thread a gogo module
> (https://github.com/xk/node-threads-a-gogo).
>
> I just wrote a blog post on fibers and threads, to try to clarify what they
> bring to the plate:
> http://bjouhier.wordpress.com/2012/03/11/fibers-and-threads-in-node-js-what-for/
>
> Bruno
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to