Where the dark side was calling, and you really liked its sales pitch? I don't know why, but this thread on the Movable Type forums hit a sore spot with me. I think it's because I have a tendency to be like a rat that jumps onto a listing ship. Let me explain...
Movable Type used to be the king of blog software, but it has since gotten its ass handed to it in the marketplace of ideas by WordPress. That happened because of a licensing issue, not a technical issue. On many fronts, Movable Type is, beyond a reasonable doubt, technically superior to WordPress. Yet that doesn't change the fact the community is just listing in the waters, without a lot of active development from outsiders like WordPress. Movable Type has a few, very good, developers not affiliated with SixApart, and the plugin development and such relies heavily on them.
Designers? Now that is a sad state of affairs. There are only a handful of us that take care of things on that front. My themes blog is one of the biggest references for Movable Type these days, and I haven't updated it in a few months. We have, for all intents and purposes, been soundly defeated by WordPress on this front. It doesn't help that the way that Movable Type handles templates wasn't designed for rapidly swapping out the markup, just the style sheets. WordPress' approach is problematic in that it makes it harder to reuse markup, but I'm enough of a realist to know that for the average user they just want to swap out the look and feel, which WordPress does well.
Security is the one serious concern that I have with WordPress. Articles like this don't make me confident, though the fact that Stefan Esser's site Suspekt is powered by WordPress gives me reason to believe that he is more confident in its progress since he was last asked about it. The only time my blog has been hacked was because of a slightly out of date version of WordPress 2.7, and that didn't exactly recommend it to me, but I suppose that could happen to any major project.
Threads like this on the Movable Type forums are problematic for me. I mean really, why should anyone have to buy a feature to password protect their entries when systems like WordPress provide that as a basic feature? I know the technical reasons for it, unlike most of the people who've criticized Movable Type here, but I still dismiss them as a classic case of making the perfect the mortal enemy of the good. The more I look at Movable Type, I find that it's got some amazingly good implementations of certain features, and I'm left dumbfounded with "a serious case of WTF" as to what happened to others. I mean, this is one of the most incredibly customizable content management systems out there in its space, and yet it has no default system for password protection of entries. Not even a crappy excuse for one.
For blogging, I have to say that WordPress is probably more than enough. I think a lot of my harsh criticism in the past comes from my being stuck working in an enterprise mindset on the job where WordPress would be laughed at as a serious content management system. That's also caused me to fail to accept the fact that Movable Type really is slow--too slow--for a shared host because it is so much more capable for an enterprise environment as a content management system than WordPress.
So who knows. I'll play with the latest version of WordPress and give it a shot. Time to be platform agnostic again. I'm finding myself with less play time these days, especially for screwing around with blog software, and if and when we have kids, that's not going to improve. Both of them have their strengths and weaknesses. So much so, that truthfully, I sometimes wonder if they really should even be seriously competing with one another.
Update [1 day later...]: I decided to investigate the possibility of using FastCGI to run Movable Type on my host, and found out that my host does technically support it, but they're having problems with getting mod_fcgid and Apache to communicate. If I can really speed up Movable Type, then I think I'll have to stay with Movable Type because it just does what I want to do over the next few years so much better than WordPress. In the mean time, if you are a Movable Type user running your blog on a reliable FastCGI host, please give me some feedback on your host!
Update [5 days later...]: Like a dilettante, I played around with WordPress 2.7, but found that it did not meet my needs on many levels. I host several blogs on one installation of Movable Type, something that you cannot do with a single installation of WordPress. I'd have had to install WordPress MU in order to come close. After a little bit of reorganization and modification, I was able to get a tighter level of organization between these blogs from the same admin console without writing any plugins, changing htaccess files, adding new database tables, installing new software, etc.
I have to agree in hindsight that WordPress is deceptive in that it is a great upgrade from Blogger, but it is a poor replacement for a real content management system like Movable Type. While it may be faster at certain things like processing comments, it is not faster for creating software, new page layouts and it is certainly not as fast at delivering unchanged content as the static publishing model that Movable Type uses by default.
If you use PHP, one of the things that is really great about Movable Type is the ability to have it generate large shared chunks of the templates as PHP includes. I've used that to save tens of megs of storage space on my host.
Recent Comments