Pillai Jaideep wrote: > All the points you have listed basically compares the benfits of a > strongly typed OO language over a weakly typed non-OO > language. None of the > points listed would matter to a person interested in > developing a simple web > based application. But that does not answer the basic question -
Well, I worked with PHP from beginning of the language and I'm working with J2EE last four years. I tend to agree with you that for simple applications with low (read none) budget PHP will probably be the best choice. For my web page I do not need anything more. But if one need to develop enterprise application PHP is poor choice. Of course you can work with MCV in PHP also, I know. I have a friends (see www.datagate.co.uk) specialized with PHP and they developed they framework with around MCV. But, let me put it this way, it is not an easy to work with OO in PHP. Java is simply OOL designed. If you are writing a J2EE application using only JSPs that will end with very bad code indeed in most cases. Scriplets from hell. But if you are using OO you code will be (or should be) easy to understand, easy to maintenance, scalable, for start. > b.Development time wise - PHP really has the most > beautiful syntax among > all available server side scripting languages. Learning time for the > language is minimal. Not so with JSP/Servlets( I mean to become a good > developer, OOPS , some of the worst code I have seen is from > JSP/Servlets ). Maybe the real truth with PHP vs. Java is in fact that PHP is an easy to use, just as you said before and almost everyone can use it... for simple things. For anything more complex you will need an educated software developer and than Java have much more sense. >d. Performance - Definitely tilts in favour of PHP because of the > overhead of converting a JSP to a servlet java source and Well, depends. > then compilation > into a class file. Though, this compilation is only one time > upon the first > request to the JSP, it is definitely an overhead. And second, This is a not a good argument. You can have a precompiled JPSs. In any case in production you will not leave that to your users. > PHP is a pure > interpreted language, means PHP source is directly converted > to executable > native code by the interpreting engine. Unlike java, whose > intermediate > bytecode format is part native and part plain ASCII to be > interpreted at And? JIT rings the bell? > in PHP. Think about it, anyone who has been working with pure java > application servers for some time would describe them as memory hungry > monsters. True. But with price for 1 GB of memory today that is not an issue. I have 1 GB on my primary workstation at home and price was reasonable. For production it is not an issue today. Two years ago you will be absolutely right. I worked with IBM WebSphere from version 2 and in that time was not so easy to obtain 512 MB memory for servers. And we work on only one shared developer servers. Today every our developer working on individual workstations with 1 GB and Pentium 4. And we got them for $1000 per workstation. --Srdjan --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.458 / Virus Database: 257 - Release Date: 2/24/2003 =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
