The catalyst docs could do with a substantial review, they haven't had much attention lately. In particular there could do with being a good index.
I think the issue with people thinking catalyst is too big/complex is that lots and lots of developers are used to a procedural approach to dealing with web applications, and have troulble with a couple of things. These are: 1. Lots of people are in the habit of writing procedural web apps, and don't feel that they want to shift over to a more OO style. 2. Some aspects of the dispatcher freak people out until they learn it (and especially until they get comfortable with chained) and this is a bit of a point of resistance. 3. Catalyst used to be hard to install (and catalyst had a lot of influence on improving the cpan toolchain during the relatively early days), but this isn't the case any more, but the perception lingers in places. Maybe the solution is in part for someone to write a Catalyst::Manual::Unsweetened in the same sprit as Moose::Manual::Unsweetened in order to gently guide people towards catalyst from something they're less familiar with.
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
