Re: Porting POE to Moose

I gave Evan the benefit of the doubt when I asked him to post here  
despite his multi-year history of abuse in IRC.  His project overlaps  
the efforts of at least two readers, and I had hoped an announcement  
would start some discussion between projects.

I assumed the change of venue might prompt Evan to act more mature, as  
it has for others.  Given the opportunity to compose a longer, more  
considered message, Evan has instead reached new depths of abrasion.

Please forgive me for not sharing your optimism or sense of humor.   
He's always like this.  It's tiresome, it's annoying, and he keeps  
defying expectations that he'll improve.

-- 
Rocco Caputo - [email protected]


On Apr 27, 2009, at 20:31, Todd Chapman wrote:

> Ok everyone. Evan made a mistake. He was probably making a joke but it
> didn't go over well. Let's give him the benefit of the doubt. I hope
> he uses POE as the start of making something really great. If not we
> still have the POE we know and love.
>
> -Todd
>
> On Mon, Apr 27, 2009 at 7:59 PM, Bill Nash <[email protected]> wrote:
>> None, any, or all of this may be true.
>>
>> But I got laid this week.
>>
>> And built three new POE engines. It was really easy because I'm  
>> smart.
>>
>> - billn
>>
>> On Apr 27, 2009, at 2:53 PM, Evan Carroll wrote:
>>
>>> Dear POE,
>>>
>>> I'm sick of pulling my hair out because of your 1989 coding  
>>> practice.
>>> I've begun packing your bags to send you to Moose-landville. My goal
>>> is to totally deprive you of blessed arrays, and closures in new. I
>>> personal yearn for the day when you lack the confusing nonsense that
>>> gives you your identity. The problem is other modules don't look  
>>> like
>>> you for a reason -- you're ugly.
>>>
>>> You're actually worse than ugly, you're hideous. You're the ugly
>>> bastard brother of the ugly duck. While you aver that smaller, more
>>> modular functions are better for an event driven systems, at your  
>>> core
>>> you're black with deception. You have the longest most ugly and hard
>>> to follow monolithic logic ever. But, wait I think I'm playing this
>>> down... See, you're more than just one type of ugly: you've actually
>>> got all the unique colors of ugly; but, unlike a rainbow they're are
>>> in no predictable order. That's right, your capriciously ugly.
>>>
>>> Above and beyond blessed arrays, why for the love of god do you feel
>>> the need to strive for object-orientation through "components." What
>>> is a component anyway?!? Why can't I just go my POE- 
>>> >new( kernel_args
>>> )->wheel( wheel_args )->add_to_wheel( new_event ). Why do I have to
>>> read to just figure out your obscure coding methodology? Why can't  
>>> you
>>> just be like everyone else. How do your individual components talk  
>>> to
>>> each other, why is it so hard to figure out what your doing when you
>>> fail to do what I want? You act like Perl's objects are an unfit for
>>> life, but in the end my code just looks like a soup of disassociated
>>> components that sometimes work, and sometimes don't. Why is it so  
>>> hard
>>> to publish a module that attaches to the POE Kernel if it is there,
>>> and if it isn't operates in a sane fashion...
>>>
>>> Join me in slaying the dragon:
>>>  http://github.com/EvanCarroll/MooseyPoopoe/
>>>  (All of the POE::Kernel::Filters are migrated and running under the
>>> test suite)
>>>
>>> --
>>> Evan Carroll
>>> System Lord of the Internets
>>
>>