Re: UP-TO-DATE Comparison of CGI Alternatives

Hello iaw4,

what you ask (an yearly FAQ dedicated to the Perl Web Panorama) will be a real gift for the community. I fear no one here around has the time and the whole view to write such a thing or maintain it.

Here at the monastery you can collect opinions: many monks have (good) experience in web programming but the number of combinations is such that seems very difficult to get out from the opinion's field.

Even if i'm not an expert in Perl Web programming I have the sensation that Dancer2 is the easier approach for the beginner (even if I remember here some criticisms about the way Dancer handles the routes definitions...).

In the proposition to help you to collect more information (opinions?) i put here some sparse material reference:

perl as a php alternative your precedent intervetion about Perl web panorama
CGI Alternatives where I put a lot of links
Dancer Dancer2 Plack PSGI on my homenode
Understanding Catalyst

In addition to directly Perl dev web related choice, i think it is worth to mention Template::Toolkit as widly appreciated tool to produce the appearence of Perl web output.

I want to put some emphasis on the ++YourMother sentence: Deployment concerns are probably the biggest hurdle for devs. I think this is damn true! Here the number of combinations become disarming.. The deployer is almost another entire job per se. Choice the appropriate way to deploy a web application is harder than choice a framework.

Plack/PSGI Application Deployment has good link on deployment (with a good hint about uwsgi)
Scalable application with perl

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re: UP-TO-DATE Comparison of CGI Alternatives

Replies are listed 'Best First'.
Re^2: UP-TO-DATE Comparison of CGI Alternatives by choroba (Cardinal) on Feb 27, 2017 at 09:19 UTC
> it is worth to mention Template::Toolkit I'd add Text::Xslate as an interesting templating option, too. If you need template inheritance (smarter inclusion of templates), this is the way to go. ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l]
Re^3: UP-TO-DATE Comparison of CGI Alternatives by Your Mother (Archbishop) on Apr 23, 2017 at 10:59 UTC
Sorry for a late follow-up but I want to ++ and add: Text::Xslate is dramatically faster than Template::Toolkit. For at least 15 years I have adored TT as a kitchen-sink mini-language and tend to use it via Template::Alloy but I have been reaching for Xslate more often lately because of its speed, it forces good View practices, and it has better web security baked in (HTML escaping is opt-out, `\|mark_raw`, whereas it is opt-in in TT).	[reply] [d/l]


Do you know where your variables are?
	PerlMonks