3 ms·
Having supervised or been involved in the build of about 300 Drupal sites I can say: Small Core! Seriously, since I didn't have to use Drupal I haven't in new
by ethank 15y ago
Having supervised or been involved in the build of about 300 Drupal sites I can say:
Small Core!
Seriously, since I didn't have to use Drupal I haven't in new projects. I found that the conflating of configuration in the database (at least in D6) made true test-driven development and agile maintenance a chore. It made good development processes more difficult than necessary.
Drush went a long way toward fixing this, as did Features and a few others, but it always felt like it was stuff added to Core to remove stuff from Core. That always felt clumsy to me.
I owe Drupal a huge amount in terms of how its use helped what I did and the artists we did it with, but the project, as most do, has grown too big at this point. It needs a reset and a focus on deployable quality, scalability and additive functionality rather than subtractive.
- mcantelon 15y agoIs "small core" a movement to decouple the framework from the product?
- ethank 15y agoIndeed. If you've ever worked with Drupal in large scale production environments, the need for this is abundantly clear. As for scope, we were launching at times 5 sites a week.
- mcantelon 15y agoAh. Yeah, I've worked with Drupal for 5 years or so and have been baffled by the orthodoxy that framework and product must be the same thing. My guess is part of it might be political: it would be harder to centrally control two projects rather than one.
- pyre 15y agoProbably more like String Theory. An idea that there must be a singular product that can satisfy everything at once. (We could even call if the Master Control Program! ;)