| |
|
Can Java CMS match the PHP ones? |
|
|
|
Written by Harshad Oak
|
|
Mar 21, 2005 at 07:36 PM |
|
Page 1 of 4 One question that keeps being asked about IndicThreads.com is that how
come you are running on PHP when you are supposed to be a Java J2EE
portal?
Honestly, we would have loved to be on Java and be able to experiment on the site using Java software and also keep generating in house articles about how we manage IndicThreads using X component and how we upgraded to Y server and so on.
However going with a Java Content Management
System (CMS) wasn't the best option for us at the time we launched and I am not sure if it still is.? While creating IndicThreads, we tried out and compared several CMSs from the Java as well as the PHP stable. Based on those learnings, below is an attempt to list some of the points that I think make PHP CMSs a better choice than the Java ones:
- Evolved:
The PHP CMSs seemed far more evolved. Mambo, PostNuke, Drupal all have huge communities and have been around for quite some time. They are also running on thousands of sites and so are very well tested. - Ease of Use:
PHP CMSs are remarkably easy to use. In 15 minutes time, even a PHP illiterate person can get a site going . I doubt if that can be done with a Java CMS. - Hosting:
Java hosting is not only costly but it is also a specialized segment. Not many hosting providers understand how Java J2EE web applications are deployed. Apache + PHP is so common that even the small hosting companies are good at it and can fix issues in no time. - Sleek:
Some Java CMSs are 10 times bigger and more complex than the popular PHP ones. If you know HTML, you can more or less figure out how a PHP CMS is working. That also makes tweaking the CMS a fairly simple task.
- Community:
The community? around Java is one of its strong points but PHP CMS also have huge community bases and so getting help from fellow users is simple. - Non Issues:
Even if we presume that PHP cannot match Java in terms of scalability, object orientation.... it wouldn't matter much to most website creators. Having a good, simple, feature rich, easy to host and maintain site, are the things that matter most.
As of today, the PHP CMSs seem to have convincingly beaten the Java ones.
Maybe while the Java world was engaged in talking of high end, super techie stuff, with the words 'enterprise', 'transactions' and 'SOA 'embedded in every sentence, the PHP guys actually went out and created a lot of simple yet very useful software.
>> PHP CMS: http://www.opensourcecms.com/
>> Java CMS: http://java-source.net/open-source/content-managment-systems
|
Comment by Guest on 2005-03-21 21:53:59
You are right , and you choiced a great cms (mambo) |
Comment by Guest on 2005-03-23 14:25:06
You are not really talking about PHP vs Java CMS's. You are talking about *OpenSource* CMS's, and only that (it seems). Commercial Java CMS's is a whole other story. |
Comment by Guest on 2005-03-23 14:37:58
I don't agree with your statements.
The deployment of a J2EE cms can be just as easy as a PHP one. All a user has to do is upload the war (tomcat) or ear (jboss) file to the webserver and the file is deployed by the Application Server.
Installing a CMS on a database could work perfectly when it works with an XML file for the data.
The argument that editing a PHP page is simpler isn't true at all. In Java there are numerous template engines that are far superior to the ones in PHP. A template page in Java has the same structure as an XML document, so it's editable with your favorite ascii editor. |
Comment by harshad on 2005-03-23 15:21:40
Point taken. Yes, I have only discussed open source CMSs.
Our experiments were pretty much restricted to the free and open-source options from both Java and PHP. If anybody wants to share some info about non open source CMSs, please do. U could ofcourse blog as part of the [URL=http://indicthreads.com/contest/140/Best_Java_Blogger.html]Best Java Blogger Contest[/URL].
Also it would be good if you register and post your comment or at least state your name in the comment. Comments from real people instead of guests are more credible and fun. |
Comment by Guest on 2005-03-24 01:30:59
I have only looked cursory at Java CMS systems since there are so many PHP ones myself. I happen to be one of those small hosting companies you mention in my night job with my day job being a Java developer. It is interesting to note though that the company I work for is finalizing its selection of a commercial Java CMS to run on top of WebSphere and is JSR-170 compliant. I'll let you know how it goes.
Back to PHP, I have to agree completely about its ease. I started using it at first a bit reluctantly to build a dynamic site for a customer and I really like it now to the point that I almost wouldn't mind building a 'large' app with it just to see it in action. With PHP's growing support of OOP, template systems and such and the fact that it is just plain fast has me excited about it. It seems sometimes that the java community gets overly excited and into heated debates about frameworks and which is better and all that instead of just using what is appropriate for the job at hand. This is also happening with scripting in the java community.
With IBM starting to support PHP via Zend and projects like SugarCRM coming along, maybe PHP will get a bigger piece of the pie.
I personally like that you are using Mambo as I'm evaluating it also for building customer sites. I am working on one now that will be using IntegraMOD (built on phpBB), but I like Mambo's potential.
If you want to brag more about your use of Mambo, let me know as I would like to hear from real users.
Robert
robert@bull-enterprises.com |
Comment by Guest on 2005-03-30 03:37:03
Hi
Every one here , I suggest you take a look at
www.jetNuke.org , its going to be PHPNuke clone in java. |
Comment by Guest on 2005-04-07 22:00:52
I looked at PHP and Java, but found Plone to have much more flexibility and functionality |
Comment by Guest on 2005-04-08 23:00:52
With CMSes, it is either PHP CMS based site or no site.
A very very minute number of software folk can manage to create and deploy a J2EE based site. While almost any software developer (even web designers) can create a PHP CMS based site, only a Java J2EE experienced person can create a J2EE based site. So the ratio might be 100:1 in favor of PHP.
So PHP works. J2EE is super, amazing, awesome... but is doesn't work ;-) |
Comment by Guest on 2005-04-11 20:29:26
Just perhaps try Jahia (www.jahia.org)... Looks like easy to install and quite ergonomic + includes both a portal and a CMS. |
Comment by Guest on 2005-04-13 11:51:32
I agree that PHP much easyier to understand. In java if you want to explained abaout object presistence you need to read a lot of documentation. In PHP you can describe it in one page. See it your self at http://www.haltebis.com/presistence_object/ :) |
<< Start < Previous 1 2 3 4 Next > End >>
|
|
|
|
Home | 
X 
