Why I switched from Drupal to Movable Type
Apr 29, 2003 16:16 · 421 words · 2 minute read
Drupal is a flexible, powerful program. They bill it as “Community Plumbing” and provide a whole slew of features, either built-in or as plugins. It supports many of the common weblog features and adds many uncommon ones: the ability to share authentication, the “collaborative book”, the RSS news feed reader, and on and on.
My decision to switch to Movable Type is certainly not based upon lack of features in Drupal. In fact, I decided to switch because Drupal has too many features and too flexible an architecture for me.
MT was very easy to setup and is extremely ease to use. It doesn’t have a collaborative book or forums or news feeds. It just does blogging, and it does it gracefully. The blogging interface is nicely laid out and the relevant section of the decent user manual is a click away. Comments don’t require users to become members of the site and are easily integrated. Templates are trivial to edit and can be edited on the web or as external files. The bookmarklets are a great timesaver and will doubtless lead me to create many more blog entries. Trackback is a cool feature that is tightly integrated (not surprisingly, since SixApart created the initial spec).
I’m sure that everything I’m getting out of MT can be done with Drupal, but with MT it’s very easy to do those things and I didn’t have to spend any real time getting it up and running. Since I’m a geek, you’d think I’d go for the most powerful tool. But, I want my blogging to be effortless and MT gives me that.
One last bit: the Drupal folks have worked hard on performance and provide a sophisticated caching infrastructure to allow a Drupal site to survive a slashdotting (as Kernel Trap has had to in the past). MT gets around this altogether by rendering out everything people are most likely to see as static HTML. I’m certain a typical Apache can push out a whole lot of static HTML and the only likely problem would be if thousands of people wanted to comment all at once, since that’s still a perl cgi.
If you’re looking to set up a web community, particularly one revolving around a piece of software you’re releasing, I wouldn’t hesitate to recommend Drupal. If you’re looking to run a weblog and want a tool that stays out of your way, MT is definitely a good choice and I can see why so many people out there are using it.