Karakas Online

2.6.2. PHP-Nuke vs. XOOPS

XOOPS is a dynamic OO (Object Oriented) based open source portal script written in PHP. According to its developers, XOOPS is the "ideal tool for developing small to large dynamic community websites, intra-company portals, corporate portals, weblogs and much more" (see About XOOPS). The developers also tell the following about their goals:

The goal of the XOOPS team is to create a Content Management System (CMS) for users and developers that installs out of the box offering unparalleled ease of use, support and management. The XOOPS CMS will be extendable by the use of modules installable through a unified admin interface. The ultimate goal of the XOOPS team is to take the best features of current CMS's and roll them into an Open Source CMS that's easy to use, extendable and unparalleled in the Free/Open Source Community.

XOOPS is (see XOOPS Features List):

The OO (Object Oriented) approach of XOOPS to Web Content Management is innovative, but also controversial. Franzisco Burzi writes in History of PHP-Nuke and Post-Nuke:

About saying that OOP (Object Oriented Programming) is a good stuff and makes stuff more stable, modular, or whatever else you want... False. OOP is good for very big projects, which is not the case of PHP-Nuke (I mean VERY BIG projects) with a lot of reusable code. BUT... any good PHP programmer knows that the use (or worse, the intense use) of objects/classes in a PHP script isn't good. PHP is not efficient managing objects/classes. At least it's less efficient than managing custom user created functions. Any decent PHP 4 book will say this to you: If you can manage to have your software working without using OOP, there isn't any reason to use objects, because of performance issues.

Last updated Sun Aug 7 21:14:12 CEST 2005 Permalink: http://www.karakas-online.de/EN-Book/php-nuke-vs-xoops.html All contents © 2004 Chris Karakas, Claudio Erba