Image via Wikipedia

While I’ll no doubt get lots of flames from Rob about this, I’m not afraid of saying that Drupal sucks as it is right now. That’s not to say it’s not getting better (for sure, it is) but a lot of problems that I and others have with Drupal stem from some poor basic design choices, which would require a stupendous amount of work to fix. Hiveminds Magazine covers a few reasons for why Drupal isn’t as good as it could be.

Now, I’m not about to go and create my own CMS using the model-view-controller design pattern, or any other design pattern. I’m sticking with Drupal for the time being, because I know with each new version it gets better. But eventually the project will reach the point where there will be little left but re-engineer the whole mess, and introduce a new, more efficient way of managing it all. You can only push PHP so far with certain patterns, and front controller isn’t one that works well with PHP, despite the success of Drupal.

Related articles by Zemanta

• Talk is silver, code is gold: Acquia's code contributions to the Drupal project
• phpPatterns: design: the front controller and php