Robert Klemme
2/21/2006 6:30:00 PM
Daniel Nugent <nugend@gmail.com> wrote:
> Uh, yeah, that's pretty much why not all code is threaded.
>
> On the other hand, in programs above a certain size, or ones that have
> graphical user interface, there usually is something else that you can
> do while you're waiting on that resource.
Like reading from or writing to another resource. Exactly. Ruby's
multithreading is only at a loss on a multi CPU machine with heavy
computation because it doesn't use more than one CPU.
Kind regards
robert