|
Re: Perl Web Development Frameworks
by gamache (Friar) on Oct 22, 2007 at 13:23 UTC
|
I did a web software project in the Jifty framework last year. In my experience, there was a very steep learning curve. Jifty gets a lot of things right and is quite featureful and magical; however, the documentation is lacking (boy, that was polite) and things can get a little shaky unless you do everything The Jifty Way.
Having worked through one project in Jifty, I am confident the next one would be live in 1/4 the time since I know the terrain. I'd recommend you do a sample project in Jifty before throwing your whole weight into it -- something with a similar set of features to what you want to build for real. | [reply] |
|
|
I had a similar experience working with Jifty. I found the transparency on the database layer very good, and was able to get a lot of mileage out of that. When it came to the actual web code, however, I found Jifty getting in my way more than helping me out. Most of our bugs tracked back to a poorly documented user permission structure. After several days spent crawling through Jifty looking for what was set wrong, we eventually decided to strip out Jifty and build up a simpler system based just on raw Mason. Even factoring in the conversion time, it was a net gain in productivity.
YMMV of course, and it should be noted we were working on a fairly simple application where rolling our own interface from scratch was not that big of a deal.
| [reply] |
|
|
I had a very similar experience regarding Jifty's user permission built-ins (and the docs which ostensibly describe them). Really, the whole project was a sequence of:
- Try to find FEATURE_X in the docs. On failure, skip next step.
- Try to extrapolate proper usage of FEATURE_X in REAL_LIFE_SITUATION_Y from the single provided line of sample code.
- Beat head against wall for several hours.
- Bug Jesse Vincent on IRC. Jesse provides the Right Way to do it in about ten seconds and 35 characters.
- Code it. The solution generally works and is elegant.
- 20 GOTO 10
I can easily imagine how keeping Mason and throwing the rest out could make your life a lot more pleasant, especially if you don't need AJAX/continuations/insulation from SQL/a pony/other features that Jifty provides out of the box.
| [reply] |
|
|
Thanks to everyone for the answers...
Monks ...keep rocking..!!!
| [reply] |
Re: Perl Web Development Frameworks
by moritz (Cardinal) on Oct 22, 2007 at 14:47 UTC
|
| [reply] |
Re: Perl Web Development Frameworks
by perrin (Chancellor) on Oct 22, 2007 at 14:41 UTC
|
In terms of demand, the most popular framework for Perl is probably Mason. That's just a piece of the picture though. You should at least look at a few of the popular ones (CGI-Application and Mason as well as the ones listed above) before making your own choice. | [reply] |
|
|
It's worth mentioning that Jifty relies heavily on Mason (and about 50 other modules).
| [reply] |
Re: Perl Web Development Frameworks
by zby (Vicar) on Oct 23, 2007 at 14:38 UTC
|
| [reply] |
Re: Perl Web Development Frameworks
by metaperl (Curate) on Oct 04, 2011 at 12:25 UTC
|
Mojolicious is my bread and butter. I cant imagine web dev getting any nicer.
| [reply] |
|
|
I traded in cgi::application for mojolicious. It has everything you need out of the box and has templating built-in (and extendable).
Mojo's biggest win is having adequate(not wordy) documentation, an instant sandbox (server,::lite, etc.), and supporting libs.
| [reply] |