On Wednesday, August 1, 2001, at 10:01 AM, Jay Jacobs wrote: > On Wed, 1 Aug 2001, Kyle Dawkins wrote: > >> Mixing HTML with Perl with SQL is bad and evil on every single possible >> level. > > If however you work in a two person company where you have barely enough > time to go to the bathroom let alone think about creating your own > database abstraction layer for a custom application and "maintaining" > code > means changing a link once a month. Then by all means embed away, and > take the quick development path over performance or maintainability. This is, in my opinion, circular logic. Perhaps the reason that you barely have enough time to go to the bathroom is that you're writing the code the wrong way. :-) > On the other hand, if you are completely broke and work on a non-profit > project and the only system you have is a P200 with 64M of Memory, then > you may want to think about avoiding templating systems, and doing > nothing > but a single module with embedded SQL with Perl and HTML. Assuming they're paying you anywhere near a living wage, their money would be better spent on modestly upgraded hardware than having you fumbling around with inefficient to maintain code. > There is always more then one way to do it, and there's usually more > then > one right way to do it. Let's keep that in mind. Agreed. However, Perl + HTML + SQL isn't one of the right ways! :-) -- -- Tom Mornini -- ICQ 113526784
