Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Actually it is not even quite right, to view Perl and Java as competitors. Although in some areas, the two languages bump into each other from time to time, for most of the areas, it is quite clear why you should choose Perl not Java, or the other way around.

Perl is very useful for what it is good at, but I don't see any sign that Perl can support enterprise level requirements easily and comnfortably. Perl is mainly still a rapid development language for various tool-level needs.

As for J2EE, although it is quite complex, majority part of the complexity is actually hidden from application developers. J2EE provides the foundation, and application prorgammers just keep adding blocks on top of it. The fact that it can be used by lots and lots of people, clearly speaks for J2EE - the complexity exposed to end users is really not too bad.

(I have had some experience with J2EE, in fact my main work at this moment is a J2EE-based application, implementation phase. My feeling is that, to first set up the development environment and deployment/running environment is really complex, but once it is set up, writing code is not really a big deal, as long as you have a fair experience with Java.)

One nature of Perl is that, it is a very strong LANGUAGE, but it appears that people rarely get into research or implementation of ARCHITECTURES based on Perl or for Perl.

Everything has what it is good at, force it into areas that does not belong to it, does not do any good. Not be able to support enterprise solutions, does not make Perl less useful. On the contrary, the fact you and me are using Perl from day to day, speaks for Perl loudly.

In reply to Re: J2EE is too complicated - why not Perl? by pg
in thread J2EE is too complicated - why not Perl? by beamsack

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (3)
    As of 2018-04-26 02:13 GMT
    Find Nodes?
      Voting Booth?