|The stupid question is the question not asked|
Re: Re: Re: J2EE is too complicated - why not Perl?by ajt (Prior)
|on Dec 08, 2003 at 12:29 UTC||Need Help??|
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!