Comments on: CMS/Portals: Java vs PHP http://www.brianburridge.com/2005/04/09/cmsportals-java-vs-php/ Brian Burridge shares his thoughts and opinions on Internet Software Architecture and Development, chronicles his current projects and areas of research, and give tips and tricks he discovers along the way. Thu, 21 Aug 2008 18:11:11 +0000 http://wordpress.org/?v=2.0.2 by: Johnny http://www.brianburridge.com/2005/04/09/cmsportals-java-vs-php/#comment-12696 Tue, 24 Jun 2008 00:07:14 +0000 http://www.brianburridge.com/2005/04/09/cmsportals-java-vs-php/#comment-12696 The problem is that Java is huge, PHP is focused. If one takes EJB out of the equation. and takes Frameworks out of the equation. The Java code is straight forward, hardly more complex than the above, and easier to read. Frameworks are killing Java... Java is not that complex, but the marketing has made everyone thing that EJB is java... that scares newbies, sp's and EJB is a swear word in many companies. EJB is NOT Java, and if the Java community doesnt have the savvy to see that EJB is killing Java... it is doomed. Java is simple, EJB is a nightmare. Add beans to the above, introspection, JNDI, SOA, and an XML parser... and it would also be something no one wants to use. There is too much crap on top of Java... Our code does the above in as many lines... in Java... its simple if you keep it simple. I share your thoughts... The problem is that Java is huge, PHP is focused.

If one takes EJB out of the equation.
and takes Frameworks out of the equation.

The Java code is straight forward, hardly more complex than the above, and easier to read.

Frameworks are killing Java… Java is not that complex, but the marketing has made everyone thing that EJB is java… that scares newbies, sp’s and EJB is a swear word in many companies.

EJB is NOT Java, and if the Java community doesnt have the savvy to see that EJB is killing Java… it is doomed.

Java is simple, EJB is a nightmare.

Add beans to the above, introspection, JNDI, SOA, and an XML parser… and it would also be something no one wants to use.

There is too much crap on top of Java…
Our code does the above in as many lines… in Java… its simple if you keep it simple.

I share your thoughts…

]]> by: Jeff http://www.brianburridge.com/2005/04/09/cmsportals-java-vs-php/#comment-7 Mon, 11 Apr 2005 23:07:29 +0000 http://www.brianburridge.com/2005/04/09/cmsportals-java-vs-php/#comment-7 Yup, this is a huge issue. I deliver business applications in J2EE and there is no question that from a business perspective J2EE development is just too expensive. The developer productivity is lower than other platforms, and while the quality and maintainability of the result is excellent we as a community need to do a lot of work on the productivity angle or someone else (some other technical platform) is going to eat our lunch. I've done some PHP and it is just too easy by comparison. Apparently the object-oriented features in PHP5 will offer (but not enforce) the ability to produce a better engineered result. The best thing we as a J2EE community have going for us is the dedication to engineering quality among the community. As I was helping one of the UI guys here resolve a session management problem, I came back to the same realization as always - in 2005, at this point in the maturity of Java, why are we solving this problem? We should be spending our time building business functionality instead. Jeff Yup, this is a huge issue. I deliver business applications in J2EE and there is no question that from a business perspective J2EE development is just too expensive. The developer productivity is lower than other platforms, and while the quality and maintainability of the result is excellent we as a community need to do a lot of work on the productivity angle or someone else (some other technical platform) is going to eat our lunch.

I’ve done some PHP and it is just too easy by comparison. Apparently the object-oriented features in PHP5 will offer (but not enforce) the ability to produce a better engineered result.

The best thing we as a J2EE community have going for us is the dedication to engineering quality among the community. As I was helping one of the UI guys here resolve a session management problem, I came back to the same realization as always - in 2005, at this point in the maturity of Java, why are we solving this problem? We should be spending our time building business functionality instead.

Jeff

]]>