Re: Lessons to learn from ithreads (was: threads?)

2010-10-15 Thread Leon Timmermans
On Wed, Oct 13, 2010 at 1:13 PM, Tim Bunce wrote: > If you wanted to start a hundred threads in a language that has good > support for async constructs you're almost certainly using the wrong > approach. In the world of perl6 I expect threads to be used rarely and > for specific unavoidably-bockin

Re: Ruby Fibers (was: threads?)

2010-10-15 Thread Leon Timmermans
On Wed, Oct 13, 2010 at 1:20 AM, Tim Bunce wrote: > I've not used them, but Ruby 1.9 Fibers (continuations) and the > EventMachine Reactor pattern seem interesting. Continuations and fibers are incredibly useful and should be easy to implement on parrot/rakudo but they aren't really concurrency.

Re: Ruby Fibers (was: threads?)

2010-10-15 Thread Mark J. Reed
On Fri, Oct 15, 2010 at 7:42 AM, Leon Timmermans wrote: > Continuations and fibers are incredibly useful and should be easy to > implement on parrot/rakudo but they aren't really concurrency. They're > a solution to a different problem. I would argue that concurrency isn't a problem to solve; it'

Re: Ruby Fibers (was: threads?)

2010-10-15 Thread Stefan O'Rear
On Fri, Oct 15, 2010 at 01:42:06PM +0200, Leon Timmermans wrote: > On Wed, Oct 13, 2010 at 1:20 AM, Tim Bunce wrote: > > I've not used them, but Ruby 1.9 Fibers (continuations) and the > > EventMachine Reactor pattern seem interesting. > > Continuations and fibers are incredibly useful and should