Mike Macgirvin
Diary and Other Rantings
Beyond Silicon Valley
   
Saturday, Jul 05 2008, 12:51 pm
Dec 18, 2005
drupal revisited
It's hard to believe that it was only a week or two ago that I was extolling the virtues of the Drupal CMS. So much has changed since then. If you recall, I made it sort of work for my needs after fixing a lot of bugs. I was all set to contribute my fixes back to the Drupal development community. But then something happened. They released a new version. Cool! I thought. I'll just download it and get all the latest stuff and maybe they've fixed some of the bugs I uncovered. Doesn't work that way. More bugs. Things that I spent time fixing are now hopelessly broken. The fixes I made can't be applied to the new code. It's all different. And Drupal works on a 'module' framework. They only provide a core application, and others in the community add things to make it do more stuff. The problem is that every time they change the core, they make it incompatible with the existing modules. Nothing I added works anymore. I have to wait for all the different modules which I was using to be re-written. Or do it myself. No thanks. They have a nasty habit of making every existing contributed module break on every version release. So you can't just write a module or fix a module and be done with it. Writing a module makes you a lifetime contributor. You'll have to fix the module over and over again and over again and over again - everytime the core application changes. Looking at the development roadmap, this is going to happen a lot. Think I'll go find another CMS package.

Or see if I can write one in Ruby||Rails in a dozen lines of code... 

Categories: software rantings
Comments? | More Actions Open/Close menu
Back
Bore, n.:
A guy who wraps up a two-minute idea in a two-hour vocabulary.
-- Walter Winchell