The Drupal Crisis
So yet another rant bemoaning Drupal's internals wanting a more elegantly decoupled internal architecture. Decoupling Drupal's internals in the ways suggested would be no easy feat and a fool's errand to even try. What's the objective? "So we can have more reasonable unit tests." That's sort of hilarious. Drupal is not exactly a test-driven culture. "So we can reuse these components in other frameworks." Seriously? You want to reuse Drupal's theme registry some place else, like wanting your bike, your car, and your golf cart to have the same size wheels because that'd be more convenient for you?<p>Drupal project leads need to avoid getting distracted by this noise. Drupal is not and should not try to be an architectural masterpiece because the typical Drupal adopter has no idea what a unit test is anyway. Addressing these complaints will add no value for the typical Drupal user. Drupal is utilitarian. Drupal fulfills the need to slap together a web site quick and make it pretty, and you don't want to know what's going on underneath. If you want architecture and unit tests then there are plenty of other frameworks out there to consider instead.