Re: [wxperl-users] alternatives to POE

[Foo JH <jhf...@ex...>]

> The connection can be asynchronous (at the socket level) without the 
> Perl code needing to be threaded.
>   
You mean a non-blocking socket call. If I understand POE correctly you 
have to alter the flow of the code so that the application operates on 
the concept of states. So we're back to cooperative multitasking, which 
I find unnecessary given the maturity and stabilty of today's OSes, 
including Windows.

>> It seems to me that everyone knows how bad threading is for Perl, and
>> rather than openly admit it, we regress (again, another arguable
>> position) into cooperative multitasking. IMHO not the right thnig to
>> do.
>>     
>
> I don't think there's any denial in play.  What do you propose?
>   
I don't think with 5.8.x there's much that can be done. I do look 
forward to 5.10/ 6.0 where I expect threading to be on par (at least) 
with the current flavours of programming languages. Perl really needs to 
have something to show for this year, imho.

Don't see me as a whiner on the downsides of Perl. There are quite a few 
workarounds on this issue, so life goes on. Even then, workarounds are 
merely short-term measures.