i think CGI::Application is great. Really great.

But I never use it. For similar reasons that you wrote Apllication::Pipeline.

but heres the thing; I can write my own baseclass framework that suits my applications perfectly.
And put in whatever handlers/plugins/doodahs i need, when i need them.

Application::Pipeline seems like a pretty neat module; I am not dissing that at all. But I see a fundamental flaw with these "just add water" frameworks; the choice between:

• warping my code round an insufficent framework
• importing and wading through a bunch of generic stuff i dont need
• spending a morning hacking a custom-fit solution

is no choice at all. Know what I mean?

update: what i mean is: IMO there is no happy medium between a simple or bloated "Application Framework". And the general mechanisms involved are too simple to appeal to compromise in the name of "Code-Reuse".