This article doesn't really say anything about how Drupal works. It just says something about the choices they have made regarding OOP in the underlying code. Many of these choices are quite similar to the ones made in eZ publish. Most of the discussion about patterns for example is valid for eZ publish as well. Contrary to what they do however, we have used OOP extensively throughout the system. This has obviously been the right choice (IMHO) considering where PHP is heading.
On the one side, this article is interesting, because it looks at a merely proceduraly programmed system from an object oriented perspective.
On the other side - what does that help? Object orientation is a paradigm, a way to look at things and a strategy how to solve problems. Not only in software development. Thus, anything can be looked at from an OO perspective. But if you don't use OO technically to solve a related problem (as Drupal seems to do) - then the whole OO paradigm is only a theoretical issue.
eZ publish is consistently designed in that matter, taking OO theory to put it successfully to the test in practical PHP OO.
Sandro Groganz
Chief Knowledge Officer
You must be logged in to post messages in this topic!
