in reply to Re^3: how did blocking IO become such a problem?
in thread how did blocking IO become such a problem?

The primary benefit is the simplified code that results from having each logical part of your application run as a simple linear flow or loop, with only that state it needs, visible to it. The second benefit is the ability to prioritise some of those logical flows over others,
Event-loop programming usually feels kind of contorted to me, too, but separate processes share both of these advantages. Better, processes make interaction between your program and the OS simpler w.r.t. I/O, signals, and scheduling than threads (which map to OS contexts in different ways on different platforms). Separate address spaces are more useful in C than in Perl, but they're still nice.
  • Comment on Re^4: how did blocking IO become such a problem?

Replies are listed 'Best First'.
Re^5: how did blocking IO become such a problem?
by BrowserUk (Patriarch) on Feb 21, 2012 at 18:00 UTC

    Re^5: how did blocking IO become such a problem? is as much a response to you as to chromatic. You both made similar points.

    You made yours first, but his was top of the list of /msg notifications :)


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?