http://qs321.pair.com?node_id=145528


in reply to RFC CGI.pm refactoring

In principle, I think CGI::Simple is a good idea; I don't think that the module CGI is cluttered by unnecessary functions (I've used most of it, and it was all necessary), but I'll go blind if I read the source. I'm not sure about its performance issues, having always worked with it - I expect raw HTML generation would be faster.

But if CGI::Simple takes out the HTML generation methods, I won't be switching. I really hate embedding HTML; the Camel's claim that perl "makes different things look different" is all very well, but embedding HTML makes code so ugly. I think CGI.pm's interface has such a distinctive style that it would obscure the code to manually generate HTML. Oh, and where's the data on the methods not being used by "a significant percentage of users"? Most scripts I've seen use them.



--
my one true love

Replies are listed 'Best First'.
Re: Re: RFC CGI.pm refactoring
by tachyon (Chancellor) on Feb 15, 2002 at 12:08 UTC

    Naturally it depends on where you work but round here, and in many other places, graphic designers generate virtually all the HTML. Templating allows coders to code perl and designers to design HTML. This way there is essentially NO HTML in your perl code be it in the form of HERDOCS or CGI.pm HTML generating stuff.

    IMHO Perl coders fall into two categories, split roughly 50:50. One half hate the HTML side of CGI.pm and half love it. No prizes for guessing which side I fall into.

    cheers

    tachyon

    s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print