At the risk of intruding upon what looks like a personal communiqué to mpeppler...

...this convenience and wealth of functionality in Perl has resulted in a decrease in ability to leverage the shell as well as a duplication of its functionality. (emphasis mine)

What functionality is no longer available such that one is no longer able to write code in this manner? Or do you mean that in the community of developers fewer people are skilled in shell scripting? What is the evidence for this, and why does it matter even if it is true? Why shouldn't one prefer to use Perl rather than an OS specific script?

Also, because so much is available within Perl, one tends to write modules to compentize complex apps instead of isolated shell scripts.

People componentize applications into modules because doing so significantly increases reusability and benefit from Perl's portability.

I would hate to have to recode all of my stored procedures whenever tables change

Changing your tables is neither a minor nor everyday activity. You must expect that changes at such a fundamental level will have cascading effects, and allocate proper time/resources to dealing with them; certainly anyway if you are attempting to utilize database optimizations like stored procedures (although IANASPE (stored procedures expert) :)

is it conceivable that the stored procedures could tax the RAM of the database server?

RAM is generally consumed by data structures, not procedures. I think you would require truly vast numbers of them to impact memory performance.

In sum, if your database server is a Pentium 133 and you change your table schemas with unusual frequency in a software package guaranteed only to run on *nix, then I can see where you're coming from. Otherwise, I think you're overly concerned with bottlenecks and maintenance issues in the wrong places.


In reply to Re: Website Application Framework with Sybase, Apache & Perl: My Thoughts by djantzen
in thread Website Application Framework with Sybase, Apache & Perl: My Thoughts by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.