|Think about Loose Coupling|
Which platform to use for CGI?by Dog and Pony (Priest)
|on Mar 24, 2002 at 16:53 UTC||Need Help??|
After a few threads around here such as CGI (Perl) vs JSP, I thought this might interest some people. :)
The other day, I met up with one of my old friends and collegaues from my last job, a guy that I think is a great programmer, and whose opinions I really value. When we were working together, we used mainly java to build (large and small) web applications. We also used perl and PHP for small stuff, and Q&D solutions. Since some of it was done in Apples WebObjects 4.5.x, it can be argued that it wasn't pure java development, but let's put that aside. For all things that matters, WebObjects done in java, can be compared to the EJB and J2EE stuff that is coming from Sun now, although it was created way earlier. It also has tons of almost unsolvable problems with scaling and performance - quite a few people use it, and advocate it, but fail to show up that super-site of theirs - it don't exist. Two years partially working with this and being on the mailing-lists tells me this is really so. Although it might have changed recently, who knows?
After leaving this company, he has a friend that is a EJB/Java servlet expert, and he got my friend lots of books and other things to study, possibly in the hope that he would come work there. After studying and experimenting quite a lot, my friend concluded that Suns proposed solution is pretty flawed: it doesn't make for speedy development, it has lots of performance issues, and although it supports clustering 100%, that clustering doesn't strike any of us as efficient, or even reliable. I'm mostly going on what he explained here, so you know. :) Given the huge price tag to get the real environments that do work, this is only feasible for large corporations that wants some really huge and complex, and has the money. Even then, my friend wasn't all that sure it couldn't be done faster in something else.
Being an old java programmer before I turned to perl, I still like java, and there are still tasks I'd gladly choose java over perl. For example, handling complex business logic, doing threaded servers and socket stuff. It might be because of what I am used to, but some things are - to me - lots easier in java. Most aren't, however... read on. :)
Anyways, he showed me this quote from an article over at IBM about choosing the right server-side scripting language:
This is the conclusion from the article that I found very nice to read - lots of it I knew, but I thought I'd share that link with you all, because it does indeed make a lot of good examples and points. And you just gotta love the punchline...
For myself, I think it is good to know as many approaches as possible, since it makes you a better programmer IMO, and even if you are "perl only", it can't hurt to "know your enemy". :)
You have moved into a dark place.
It is pitch black. You are likely to be eaten by a grue.