I know there are several comparisons available, but still i want to ask, what is that which can be done in J2ee and in through php? There must be a reason we are choosing a language that is more difficult to program and all j2ee servers are much expensive than php servers.
Using PHP is like using JSP without Servlets or any of the rest of the JEE ecosystem. No thanks.
Joined: Sep 21, 2010
I still dont get it. They say for large scale applications j2ee is more useful whereas PHP for small scale. However, there are a number of sites which are large and made in php. Example facebook. What does largescale mean here?
Gaurav Wadhwani wrote:still, why should i use j2ee if php is much easier.
If you're looking for serious answers, it would be best to stop loading your question.
I've developed in both PHP and in Java and I don't think PHP is any easier than Java. For some things, it's harder.
So, maybe the question should be: Why are so many people coding in PHP when Java is so much easier?
Better yet leave out your opinion as to which is easier and just ask for the comparison.
Better yet still, search Google and read one of the hundreds or thousands of comparison sites and threads that are already out there.
Gaurav Wadhwani wrote:I still dont get it. They say for large scale applications j2ee is more useful whereas PHP for small scale. However, there are a number of sites which are large and made in php. Example facebook. What does largescale mean here?
Just to clarify the point made above, I am posting something I came across while trawling on the internet.
Facebook has realized that there are downsides to using the LAMP stack. Notably, PHP is not necessarily optimized for large websites and therefore hard to scale. Also, it is not the fastest executing language and the extension framework is difficult to use.
Facebook’s backend services are written in a variety of different programming languages including C++, Java, Python, and Erlang.
Just to answer the specific question raised here. PHP will not be able to scale on it's own it will need the support LAMP stack, whereas in case JavaEE I do not really have to look around for scalability. JavaEE itself provides me help in taking care of it. Hence, it is suggested that for largescale application use JavaEE, while PHP can cater to simple, straightforward, small applications.
My thought would be comparison of PHP and JavaEE is absurd. If at all you want to compare, do so between JSP and PHP, though not really exact, they are almost identical in terms of their responsibilities.
Never Remember the failure
Never Forget the mistake
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com