I really feel like drupal is a great example of the average php programmers way of thinking... Why has no one built a robust cms ontop of cakephp that's gotten popular? Cakephp is the closest you can get to developing on rails for PHP (which is a good thing) It's always on my list of things to do but I get sidetracked with shit that makes me $...
Despite being a "content management framework", the core doesn't actually save you from writing code. You still have to write CRUD code, still have to manage validation, still have to define your own themables. That is, unless you use CCK/Views, which is pretty much developer-hostile lasagna and slow to boot. And it'll look like ass, unless you have an ubertalented designer who also knows PHP (i.e. a "themer", a role which doesn't exist elsewhere). And the one part that you would actually want to contextualize, i.e. the content UI, is shoehorned into the node/edit form with zero choice.
Despite the promises of the hook system, Drupal lacks the ability to swap out components. If you wish to leverage part of the page generation process for another purpose, you have to reimplement everything that comes after. Alter hooks are terrible tools for building reliable behavior, since they require you to actively fight against other parts of the system instead of just turning them off. If you don't share Drupal's assumptions about user accounts, you're fucked, unless you feel like trapping and erasing UI messages is a productive use of your time. And don't even try to maintain the resulting code.
Despite being billed as having a "solid core", Drupal's irreplaceable innards are actually pretty fragile. Form API is near impossible to debug and fails silently at the drop of a hat. The node system doesn't even let you reliably do programmatic saves. The user system is a terrible misdesign that mixes front-end presentation details ($category) with low level data manipulation. The global $user object is actually a useless fake, waiting to trip you up.
Entire portions of Drupal were created in a theoretical vacuum and released without any serious working implementations. For example, install profiles: they are executed in an incomplete pseudo-Drupal environment where it's actually impossible to do certain simple things due to static caches and dysfunctional APIs. Another example: Form API process functions with complex datatypes and dynamic AJAX manipulation. Theoretically possible, practically a nightmare.
The problem can be summarized quite effectively: out of the box, it is impossible to make a slick, modern website with Drupal, i.e. something that looks and feels like 2011 rather than 2001. It's only useful if you're already planning to write a lot of custom PHP/HTML/CSS. Otherwise you have to be happy with terribly designed contrib components that are insecure, don't scale and have bad usability. This is not surprising since Drupal has been in incremental-improvements-mode since 2002 (i.e. Drupal 4.0) and the few architectural improvements made since then were designed with only one purpose in mind: to support what Drupal already does, rather than being solid components of a CMF.
Doing Drupal will stunt you as a developer, overburden you as a designer and frustrate you as a user.
As I responded to the comment below, I'll just save a few point for here. I don't know how much you've been following Drupal 7, but this really reads like a laundry list of complaints of issues that have been addressed since you were working on Drupal.
I'm not even going to take the time to go over where I think you're wrong and which issues have been fixed. I'm sure you think that anyone that still uses Drupal has their head in a microwave, but complaining about the problems that were there in the releases you worked on instead of discussing the fact that people stuck around to fix many of them, is just poor taste.
Doing Drupal will stunt you as a developer, overburden you as a designer and frustrate you as a user.
This should read: "Doing any single (framework|cms|platform) will stunt you as a developer
0
u/midri Jan 05 '11
I really feel like drupal is a great example of the average php programmers way of thinking... Why has no one built a robust cms ontop of cakephp that's gotten popular? Cakephp is the closest you can get to developing on rails for PHP (which is a good thing) It's always on my list of things to do but I get sidetracked with shit that makes me $...