Ultimately, I read your post and I merely think "problems? What problems?" Perl is doing just fine without a standard ORM or a standard IDE or a standard framework or anything. Just like every other really successful open platform, in fact -- look at C++, look at Java, look at Python, none of them have a single standard framework or a single standard IDE. The only cases where lockin is accompanied by any sort of success are certain languages peddled by a certain monopoly, which shall remain nameless for purely pragmatic reasons: I can't type their names because I can't find a hash key on this damn Mac keyboard. (Good thing I'm not writing any Perl, or it would be decidedly low on comments...)

And to pick up on a slightly irrelevant aside:

Is there a Gnome equivalent to the super-simple Tortoise-SVN shell extension for Windows? Right-click->SVN->Update doesn't get any easier.

Really? It sounds quite complicated to me. Certainly more effort than just typing "svn up". The command-line version also has the advantage of working everywhere, whereas if you insist on non-standard GUIs you'll be at a loss again when you find yourself working on a Mac one day...

In reply to Re: On the scaleability of Perl Development Practices by Anonymous Monk
in thread On the scaleability of Perl Development Practices by jdrago_999

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.