[Catalyst] Problem with C::E::Apache and apache2/mod_perl2

[Nilson Santos Figueiredo Junior]

On 3/22/06, Scott Karns <scottkinsf at yahoo.com> wrote:
> That's it so far. Whew, I didn't expect moving from
> the built-in engine to apache2/mod_perl2 would be so
> much fun ;)

I know that instead of whining I should try to help, but I think this
sort of things should be considered top priorities by the ones who
actually maintain Catalyst.

In the last few days some people got bitten by Catalyst behaviour in
fairly day-to-day tasks, such as session handling, deploying (mod_perl
and fastcgi), weird builtin server interaction with IE, and so on.

I really wanted to see Catalyst striving in the rapid web development
arena but I think these incosistencies will end up scaring away anyone
who's actually seriously comparing all the current alternatives (and
not just following the hype). I even go as far as dreaming of the day
when Catalyst is generally regarded as a good known framework and this
could result in Perl being again considered as more than a language
whose purpose is to spit out unmaintainable applications or
quick-n-dirty hacks.

As I said, I know what sort of response this will probably get (if
any). And I'll probably even agree with those responses. I actually
tried to do some small stuff to help (some Catalyst plugins and an
HTML-Widget "addon") but I really feel that I wouldn't be able to help
much with the "Catalyst core" (even if because of time-constraints),
and hence I rant about this.

Don't get me wrong, I think Catalyst is wonderful *for me*.
But it should also be wonderful for everyone else.

-Nilson Santos F. Jr.