On Fri, Jul 18, 2003 at 01:06:03PM -0700, Damien Neil wrote:
> Also, given that asynchronous IO is a fairly unpopular programming
> technique these days (non-blocking event-loop IO and blocking
> threaded IO are far more common), I would think long and hard before
> placing support for it as a core design goal of the VM.
What makes you think that Dan hasn't already thought long and hard about AIO?
This design issue has been settled for months now. And if you don't
think it's a particularly *good* design decision, think about this quote
from Alan Perlis[1]:
Symmetry is a complexity-reducing concept (co-routines include
subroutines); seek it everywhere.
AIO with files simplifies *all* IO handling. You get sync IO through a
thin wrapper over AIO. Socket IO is already async, so why have multiple
incompatible models? Why repeat the mistakes of the C standard library
for the umteenth time?
Z.
[1] Alan Perlis: (n) definately not an idiot
