This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi, I am interested in finding out some comparions in using Java (servlets/JSP) as opposed to Perl for creating dynamic web content. More specifically, I am interested in comparisons of speed and server load (CPU usage and memory usage). Currently, we have some web based applications that use CGI scripts written in Perl and accept data via form parameters and store the info in text files. There are other CGI scripts that parse these files and extract necessary information for reports. I am interested in seeing if we could do this using Apache/Tomcat and mySQL or Postgres as opposed to Perl and text files. I was therefore asked about performance issues of both methods and that is why I am asking you guys/girls about the advantages and disadvantages of each approach. I think the stability of each architecture is also going to be an issue. Personal experience would be good, but even just pointing me towards some info describing pros an cons of each approach would be good to. Any help is appreciated. Regards, Chris Mooring
I can only give you my opinion and cannot be totally sure but if all your server side code is written in PERL which is a scripting language then my best guess is that a combination of JSP and servlets would perform better, especially if you do most of the work in the servlets. Besides, PERL SUXXX!!!
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
you do most of the work in the servlets. Besides, PERL SUXXX!!!
Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0672324261/ref=jranch-20" target="_blank" rel="nofollow">Ant Developer's Handbook</a>
Joined: Jan 17, 2001
Sorry for the last post, I pushed the wrong button. "Besides, PERL SUXXX!!!" Michael, I'm surprised with all of the good reasons to move from CGI to JSP/Servlets that you would have to resort to such rhetoric. Perl is a great tool and I'm sure it has served Chris's purpose up until now. Chris, what problems are you experiencing that make you feel that you need to move to JSP/Servlets?
Joined: Jan 30, 2002
Sorry, I get emotional sometimes. Actually I'll admit that I still use PERL sometimes in Windows because there are no native regex facilities like in UNIX (gosh I miss UNIX!) Let me restate my feelings on PERL in a less crude manner. Having programmed for nearly 30 years and having only absolved myself from the Wild West mentality and poor programming habits we were taught in the early 70's only within the last few years, I feel languages like PERL are too open-ended and allow programmers to contiue in or creep back into those bad habits. So I'm afraid that I'm not a
Hi again, The reason I was asking is that we have a number of intranet based applications here that are written in Perl. These applications capture information and store them in text files for the main part. Reports are generated by parsing these text files to extract the required info. I was wondering if, in future, it would be better to write these programs in Java. I thought that the average programmer with some C or C++ experience would be able to pick up java programs easier that Perl. I also thought it'd be nicer to store info in a database and make the info more searchable. Although I think that would place a performance overhead on the applications. At the end of the day, it's no longer such an issue. I've been told that we have plenty of Perl skills here to maintain these scripts if need be. I've also been told that there are Perl API's that allow database access etc as well, so there are no compeling reasons to move away from Perl. Oh well, thanks very much for your replies. Chris