I haven't used Reaction and I got the feeling the last I checked that I should not yet but I and a few others will answer Catalyst questions here (when I know the answers; the list is also quite good and responsive).
Using Catalyst (and DBIx::Class) in the last two days I ported the DB interaction (models/schema), login, splash, and a couple of forms of a legacy app. 80% of the time was spent on config settings and CSS. I expect to have almost the whole application ported by New Year's. All of it with tests (or so I say now but I've been keeping up pretty well) and much more stable than its prototype and doing things the old one couldn't like UTF-8 data and deployment with configuration changes instead of hard coded Perl changes per client.
For your first Catalyst project, that timeline is unrealistic. It has a learning curve; as does DBIC. But once you're in it it's freakishly pleasing how you can do things like an RSS/Atom feed in 5-10 lines of easy to read (in the context of the app and model) code. And how easily you can graft in legacy code and fix it when you have time. In an app I wrote a year ago I had a bunch of file handling embedded in controllers. I recently went back and broke it out into model classes and made it configurable (another strength of Catalyst; the configuration can come from several places in several formats and be easily overridden by location or whatever you please).
Catalyst can feel like an uphill battle at first but once you're sitting on a running app you'll be really glad you made the jog.
In reply to Re: What's your reaction to "Reaction?"
by Your Mother
in thread What's your reaction to "Reaction?"
by locked_user sundialsvc4
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |