4 ms·
I think we're on the same page more or less but there are a few points I'd like to clarify: 1. I'm aware that Drupal is a CMS. 2. I don't find myself writing
by knieveltech 16y ago
I think we're on the same page more or less but there are a few points I'd like to clarify:
1. I'm aware that Drupal is a CMS.
2. I don't find myself writing a lot of custom code on my Drupal projects and that's the entire point (for me anyway) of using it as a dev framework.
3. You have a few thousand developers of various skill levels submitting modules and the quality is absolutely going to vary from module to module, this is unavoidable. Learning to vet your modules carefully and taking a less is more approach with module installation is part of the learning curve.
4. Drupal's internals are a steaming pile compared to what, exactly? Ever taken a look at Wordpress's core code? All code sucks.
- rfugger 16y ago> Drupal's internals are a steaming pile compared to what, exactly? Ever taken a look at Wordpress's core code? All code sucks. Yes, and I'm sure Joomla's code is terrible as well. On the other hand, I can most often peer into Django's internals comfortably and see exactly how it is working, and extend that as needed.
- JayNeely 16y agoAnd this was the main problem for us. Drupal's internals were a mess of multi-layered abstraction and unclear organization. Wordpress's core code has some frustrating choices in it, but even I as primarily a non-developer have been able to find what pieces of code in the core are causing something to happen, and how to change them if needed.