Beefy Boxes and Bandwidth Generously Provided by pair Networks Bob
Think about Loose Coupling
 
PerlMonks  

Re: J2EE is too complicated - why not Perl?

by allolex (Curate)
on Dec 06, 2003 at 22:07 UTC ( #312813=note: print w/ replies, xml ) Need Help??


in reply to J2EE is too complicated - why not Perl?

Ah. For once I have all the answers ;)

It seems that many J2EE developers are disgruntled.

Well, the nature of Perl is to keep people gruntled. It might not be very couth to say it, but Perl is really a programmers' language at the very least for its superior expressivity.

Some blame J2EE for the exodus of jobs from the USA due to customer dissatisfaction.

Yes, J2EE is responsible for that and more, while Perl has contributed to resolving problems of world hunger (It's paying my bills) and promoting world peace through programmer satisfaction. The customer doesn't care, just as long as things work right and don't cost too much.

It seems that many J2EE developers feel that they where better off before moving into J2EE and evaluate J2EE as a failure.

Yes and yes! And why did that discussion thread page only render correctly the second time I loaded it? Could it be that those Java Server Pages (probably using a full J2EE stack to do some simple parsing and formatting) are overloading the poor machine?

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.

People have been announcing the death of Apple for 25 years and it still a superior product.

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.

I really like what you are saying here. If you look for SAP modules on CPAN, you can see that Piers Harding has been, well, hard at work. (I think he owns all of the SAP modules). You should have a look at his site. It think Perl's advantage in this area is the amazing amount of modules on CPAN.

--
Allolex


Comment on Re: J2EE is too complicated - why not Perl?
Download Code
Re: Re: J2EE is too complicated - why not Perl?
by DrHyde (Prior) on Dec 08, 2003 at 10:09 UTC
    I really like what you are saying here. If you look for SAP modules on CPAN, you can see that Piers Harding has been, well, hard at work...

    We've been using SAP::Rfc at work, and it's jolly good indeed. We're using it to replace the SAP Business Connector which is written in Java and about which I have muttered here before (see Correcting the SAP Business Connector).

      As the first member of the above "we" to use Piers Harding's SAP::Rfc, I can say that using Perl in favour of a Java product has been a breath of fresh air

      We have a project that uses an Apache/Perl front end running on a Linux box to talk to a SAP/AIX system, via a Java based XML middleware tool called SAP Business Connector (BC). Some of our problems are not the fault of Java, but even then it's an evil product to use.

      It's very slow. The visual development interface makes easy tasks easy, and complex tasks impossible. So it's good in a demo, but hard in practice. It's XML processing is painfully slow when compared with Perl's, Perl is constantly waiting for data from BC. It takes for ever to develop and for ever in use!

      It's hard to debug. While you can step through the flows, you can't easily print it out and read it on paper, or even see it on the screen, where you can see graphically only a tiny chunk of "code" at a time.

      Last week we need to implement a new feature. The SAP BAPI was written in a morning, but converting it's interface into XML was proving very hard, so instead we used SAP::Rfc. We had a command line prototype within 15 minutes, and after a day's playing I wrote a 120 line Perl script that takes user input, talks to SAP, and spits out a fully formed HTML page. It's SO EASY TO USE, and I like XML/XSLT!

      I would not advocate Perl as the solution for everything, but buzz word compliant technology does not guarantee success either!


      --
      ajt

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://312813]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (7)
As of 2014-04-19 08:42 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (478 votes), past polls