nperez

I have no idea what you are talking about, but it seems angsty. Let me get a couple of points straight:

"as Perl software was not simply and practically written, and was often faulty despite a extensive testing and distribution system"

So you decided that the CPAN sucked and so you wrote your own? What faults? What's not simple or practical to one of the largest online collections of software modules in the world that adheres to the free/open source software ideals?

Ever heard of Not Invented Here? You suffer from that significantly. 

Then you go on to berate an open source developer because he won't recognize your unbound awesomeness and intellectual prowess. Because obviously, you have the answer to all of the projects problems. 

nperez

Stolen from Kent Cowgill

" Settings for perl stuff.
189 	" perltidy things! true, perl-support provides this, but i had gotten
190 	" used to hitting "_t" to run my source through perltidy.
191 	nnoremap <silent> _t :%!perltidy -q<Enter>
192 	vnoremap <silent> _t :!perltidy -q<Enter>
193 	" instead of man pages, read perldoc on hitting K over a keyword!
194 	autocmd BufRead,BufNewFile *.pm,*.pl,*.t,*.ptml  setlocal keywordprg=perldoc\ -f
195 	" type "#!P<CR>" in insert mode, and it expands to a default perl fileheader

nperez

I just had a wild thought. Moose-ifying POE::Filters means that if you are stacking filters and require a thin 
shim between filters, you no longer need to insert a whole new filter. Simply subclass the filter that needs its
 data slightly transformed, and apply advice to the get_one()/put() methods, then insert where you would the 
original filter. Very clean.