more useful options PerlMonks

### Pro/Cons Catalyst/Mojolicous/Dancer

by AlexTape (Monk)
 on Aug 01, 2013 at 10:59 UTC Need Help??
AlexTape has asked for the wisdom of the Perl Monks concerning the following question:

Omniscient Monks,

i investigate some time in balancing reasons pro/cons for
different web/cgi perl frameworks.

best known frameworks are:
- catalyst
- mojolicous
- dancer

what are your experiences with these frameworks? what can you tell me about usability/bugs/features?

kindly perlig

$perlig =~ s/pec/cep/g if 'errors expected'; Replies are listed 'Best First'. Re: Pro/Cons Catalyst/Mojolicous/Dancer by trippledubs (Hermit) on Aug 01, 2013 at 14:12 UTC I prefer Dancer. Easy to get started, easy to extend, and the features that you start reaching for after awhile are there and not too hard to learn. The best example I've found is looking at the Perl Dancer Web site code itself, available at https://github.com/PerlDancer/perldancer-website/ That way you can look at the web site and the code to see exactly what it produces. Once you start templating it becomes very efficient to add content to your site instead of learning how to use the framework. Re: Pro/Cons Catalyst/Mojolicous/Dancer by scorpio17 (Abbot) on Aug 01, 2013 at 13:09 UTC Don't forget CGI::Application - it's pretty good, too. Of the others, Catalyst has the steepest learning curve, and the greatest start up overhead (many modules to load), so it may appear slow unless you run it under mod_perl or FastCGI (i.e., not my first choice for use in a shared hosting environment). Re: Pro/Cons Catalyst/Mojolicous/Dancer by sundialsvc4 (Abbot) on Aug 01, 2013 at 12:13 UTC Reckon I have both sworn by, and sworn at, all three of ’em in my time. Now, my own perspective might be a wee bit unusual because, in all cases, these were existing projects, that had all lately fallen on some hard times. They had been around for several years, were all in revenue production, and had been built by someone else who had since gone on to greener glades. (In one case, all the way to the Elysian Fields ...) In the case of Mojolicious, it seemed to have been a case of too-early adoption since that framework really wasn’t yet mature-and-stable at that time. But the frameworks were all doing their job acceptably well, and they still are today. “Bugs,” per se, in all three cases, should not be a problem. At least not with respect to their code, heh. But it’s extremely important at this stage to look for a smooth fit to the entirety of what you want your web-site to do. Every framework, so to speak, “has attitude.” The designers have one notion of how something “should” be done, and they designed and built the software to do that, and in that way. (Incidentally, I do not mean that comment “personally.”) Like every architect does, they put scopes and boundaries on the project (all in different places), and to go outside of these they provide some sort of “plug-ins” and this is where you can run into trouble if you’re going to. Scope out your project completely and see what fits best. Don’t just think-so ... prove it. Last comment is to, from the start, get to know Test::Most, and Selenium, extremely well. Re: Pro/Cons Catalyst/Mojolicous/Dancer by Anonymous Monk on Aug 01, 2013 at 11:01 UTC i investigate some time in balancing reasons pro/cons for Why not share what you investigated? cause i´m never worked with one of these. atm i´m looking at examples and try to see what is more e.g. intuitive. i´m scratchin on the surface.. anyway i thought about getting some insider/developer infos before i start to working with any of these frameworks. thats the reason why i am not sharing my "little"/partial knowledge.. kindly perlig$perlig =~ s/pec/cep/g if 'errors expected';
Re: Pro/Cons Catalyst/Mojolicous/Dancer
by Anonymous Monk on Aug 02, 2013 at 01:20 UTC

Hi,

I tend to find these things come down to personal prefrence. Give them all a good go, including building a small tester with all of them.

One important consideration that can be overlooked. If you have been put in charge of a team, check out their experience.

If they are all good with one of the frameworks, you have your answer.

J.C.

Maturity trumps personal preference

In my short experience I've found Dancer to suck more on a technical level -- and the developers know about it, that's why they're writing Dancer2

Create A New User
Node Status?
node history
Node Type: perlquestion [id://1047425]
Approved by Corion
help
Chatterbox?
 [LanX]: I want the command line in the history [tye]: -Mouse [Corion]: Option a) would mean launching cmd.exe /k c:\path\to\ batchfile- launching-perl- script.cmd. Option b) would be to add pause as the last line of said batch file. [LanX]: First day after holidays ... and already stressed by the fact that colleagues changed stuff without communication ... apparently I'm the only one trying to fight entropy [Corion]: LanX: The command is always in the history if you typed it in before. If you didn't type the command into the command line, it will not be there. I think there is doskey which can stuff command lines into the history LanX damns the cult of CB ;-) LanX WTF WTF WTF [LanX]: please forget my last 3 posts [LanX]: Yeah option a doesn't go into history [LanX]: probably I need to teach the app to restart after C-c Kill

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (9)
As of 2017-03-27 15:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
Voting Booth?
Should Pluto Get Its Planethood Back?

Results (320 votes). Check out past polls.