3 ms·
If you've every worked with any large scale Drupal deployments, you'll know that its module system doesn't scale very well in terms of maintainability. You basi
by clofresh 18y ago
If you've every worked with any large scale Drupal deployments, you'll know that its module system doesn't scale very well in terms of maintainability. You basically end up with thousands of functions in the global namespace with little to no abstractions. Rails and Ruby in general are well known for their syntactic sugar, allowing for more clear and maintainable code.
- knieveltech 18y agoI have worked pretty extensively with Drupal and I don't agree with your assertion that the module system has maintainability issues. Performance issues, absolutely, but it's quite maintainable.
- dejb 18y agoAny namespace issues are largely dealt with by naming conventions such as prefixing function names with the module name. For the 'hooks' that connect modules to the rest of Drupal this is compulsory. You can structure your own code pretty much however you want including using classes or whatever php allows etc. So while it isn't perfect I don't see it getting in the way too much of module development. You could of course argue that Drupal would be more extensible if it did use OO or some other paradigm but I see that as a slightly different issue.