I find it implicit in where you go with the piece after that that in some places it's important to constrain the damaging side of innovation, and in others it's important to encourage the positive things innovation has to offer.

That's an excellent way to phrase it. I've commonly said of RUP (though I think it applies -- if less so -- to Java): "the advantage of RUP is that it protects you from bad programmers; the disadvantage is that it also protects you from good programmers." The constraints inherit in "enterprise Java" may provide some level of protection from mediocre developers, but (as you said) it also somewhat hampers good creative developers.

It's a tightrope walk to give a development team the freedom to create while protecting the customer from the wrong kinds of creative. It's much more a social problem than a language choice problem, of course: it almost merits its own meditation.

Thanks for sharing your insights!

<–radiant.matrix–>
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet

In reply to Re^2: The Enterprise Language Trinity by radiantmatrix
in thread The Enterprise Language Trinity by radiantmatrix

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.