> > My big requirement is for lightweight microthreads... > > Parrot's going to live on top of the system thread library, so you may run > into some issues that way. Not all systems can handle lots of > threads--many of them (including Linux) have very low limits relative to > what most microthread-based systems expect.
But Parrot has continuations. Doesn't this gives me (cooperative) microthreads? (with a little work on my part). > I'm still not 100% sure about serializable continuations, though I expect > so. Weather or not I go for Parrot, I would very much encourage you in this direction. The world needs: * Long lived processes (long could mean years!) * ACID transactional processes * Mobile processes > (They may be rather large when serialized, though) With a deep stack, this is inevitable right? Or are you saying that Parrot would be worse than other systems in this respect? Thanks for you advice. Tom.
