On May 3, 2012, at 8:41 AM, Mark Haney wrote: <moderator hat> I think we're at the point where everybody in this thread needs to take a deep breath and step back from the keyboard for a bit, maybe go for a walk or something. The phrase "more heat than light" is coming to mind.
(Aside for anybody else considering replying to this: you should probably let it go. (If you think I'm talking about you, I probably am. Let it go. Thanks.)) </moderator hat> > I'm really quite intrigued by the assertion that CGI is very seldom used. There are two senses of "CGI" that are being conflated here. There's CGI-the-protocol -- i.e., dynamic web content -- which is used all the time all over the place. And there's also CGI-the-Perl-module a/k/a CGI.pm -- which isn't used all that much anymore by people who do a lot of web programming. You can do CGI in Perl without using CGI.pm. > Based on this entire thread, the Template Toolkit is used entirely for > building websites in perl. I'm sorry you've gotten that impression, but that's incorrect. TemplateToolkit is a generic templating framework. It can be used for anything involving a template plus some data producing some output. Even in the cases where it is used in a web programming context, TemplateToolkit may not be producing *HTML*. My current work project is a web application. It uses TemplateToolkit exclusively -- but it produces HTML output, XML output, and sends email. All generated using TemplateToolkit. > But, it appears that I'm getting contradictory messages here, none of which > make me feel particularly comfortable with continuing to use perl for my > project. I'm sorry you're not having the best experience getting your questions answered on the list. I really am. I've considered jumping into this thread before, but I've been very busy with work and I was hoping things would straighten out on their own. Seems that isn't happening, and again, I apologize. That said, this thing you've done, a couple times now, of "I'm just gonna leave and go use PHP" -- that's not helping you to get better answers. If you can solve your problem more quickly and easily using PHP, by all means, use PHP. (And feel free to substitute "Python" or "Ruby" or "Haskell" or "Java" or "Scala" or "cuneiform tablets" in for "PHP" in that sentence.) This list isn't about evangelizing or advocating for the use of Perl; it's about helping people who have decided to use Perl to use it effectively, to enjoy using it, and to use it "properly" -- in that order. (The scare quotes around properly are there because this is Perl and our motto is TIMTOWTDI.) > I'm being given the impression that perl isn't used the way I'm intending to > use it. Based on the description you have given of your problem, it could easily be solved with Perl. Part of the problem here is that you seem to have latched onto a particular approach to solving your problem, and you are not terribly open to hearing that the approach you have selected is not the best approach *if your tool of choice for solving the problem is Perl*. Rather that phrasing things as "here's my problem, here's my approach, how do I do that approach with Perl?", consider phrasing them as "here's my problem, how should I approach that if Perl is my tool?" > In other words, I'm just about at the 'I give up' stage and moving everything > to a platform that has a good helpful community. My apologies to those that > have helped. It's been greatly appreciated, but I'm about as frustrated as I > can possibly be. Again, I apologize that you've had a frustrating experience here and I hope that after a bit of a break and some reflection, you'll come back. I would suggest perhaps starting an entirely new thread with a fresh attempt at explaining what you're trying to achieve, and we can let this thread go. thanks, john. -- John SJ Anderson // geneh...@genehack.org -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
