Sorry for the misunderstanding, I will reword. I didn’t bash CGI and if you knew me you’d realize I’m an apologist for it and have answered many, many questions here with code using it.
My point is: it’s basically perl4, mixes concerns too much (controller and view and even model and webserver, as implied in this thread’s proxying answers), and has nearly nothing but godawful usage examples in the wild. There is a real drag on learning and grandfathered-gotcha-time that could be spent learning and improving newer stuff. zentara’s Vars bug in this thread is on point. I’m advocating choosing modern tools because they are easier, facilitate learning and sharing across other languages like Python, and are tremendously more friendly to plug-n-play extensibility.
A good work environment is going to practice some parsimony with its tools and frameworks. Using Dancer AND Mojolicious AND CGI::Application AND Amon AND Catalyst AND raw Plack AND CGI is not the way to run a shop with multiple devs. CGI being the oldest and least well abstracted should be right out.
I already said I use and will continue to use CGI for personal stuff, testing, terse code answers here, and guaranteed one-offs; it’s still in my default code template. Far from bashing it, I love it. I’m giving what I feel is good advice and the kind of thing that would make the average Perl web development career better; including mine.
In reply to Re^13: Shortest/quickest way for Perl to take POST data it receives and send a POST request with this data to another URL?
by Your Mother
in thread Shortest/quickest way for Perl to take POST data it receives and send a POST request with this data to another URL?
by tunafish
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |