<div dir="ltr">umm from something they're *more* familiar with.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 4, 2015 at 7:43 AM, Kieren Diment <span dir="ltr"><<a href="mailto:diment@gmail.com" target="_blank">diment@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>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.<br><br></div>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:<br><br></div>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.<br><br></div>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.<br><br></div><div>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.<br></div><div><br></div>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.<br></div>
</blockquote></div><br></div>