comment on

There is an interesting discussion thread on theserverside.com related to the complexity of J2EE.

It seems that many J2EE developers are disgruntled. Some blame J2EE for the exodus of jobs from the USA due to customer dissatisfaction. It seems that many J2EE developers feel that they where better off before moving into J2EE and evaluate J2EE as a failure. Some defend the complexity of J2EE as a necessary evil for things such as transactions, authentication etc.

I remember reading that Perl was supposed to fade away and that Java would become paramount. Yet it seems that Perl continues to thrive and grow as Java seems to be failing on the server as it has on the desktop.

My question is how suitable is Perl for high-end (like Banking, Insurance etc)applications. Is there an application server like approach available for Perl and how do Perl developers manage transactions and authentication and other activities thought to be only managed by J2EE and proprietary solutions such as SAP.

_{janitored by ybiC: Grudgingly formatted for legibility using balanced <p></p> to replace foul <br> tags}

In reply to J2EE is too complicated - why not Perl? by beamsack

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks