Fibers are not blocking. This is not the same thing. If the issue is that writing callbacks is hard and it's easier to reason about multiple stacks, threads, or other techniques that appear blocking but really are not, then sure use fibers. But like I already stated. True blocking is an entirely different model. It's much simpler, but much less parallel.
On Thu, Apr 5, 2012 at 10:58 AM, Alexey Petrushin < [email protected]> wrote: > We already have it with fibers, synchronous code can look like this > http://alexeypetrushin.github.com/synchronize > > It's also possible to write synchronized wrappers for all node core > libraries (say name it like `fs-sync`, `dns-sync`) and in the code it will > looks like it's just an usual synchronous methods. > > But, do You really need it? That's the question. Tools like fibers allows > You to cut 90% of fat caused by async functions, and remaining 10% are > usually too small problem to care about it. > >> -- > 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
