So for a hot second there… okay, maybe a hot minute… I thought to myself: “I’m going to migrate my blog to WordPress.” WordPress has been getting a lot of press lately (pun!) not just on the interwebs, but also amongst my peers. It’s got a nice, simple UI that I can appreciate, it has a very well-developed plug-in library, and it (apparently) gets updated a heckuva lot more often than MT (or pretty much any of the other blog engines.) These points appeal to me. I like actively developed software. It makes me feel like when some new and unbelievably awesome social networking site comes on the scene, my blogging software can ‘keep up’ and ‘plug in’. Right.
I did a bunch of research, opened up a whole series of windows, loaded up all kinds of articles on migration, and prepared myself for a task that I’ve already done once before (and it was hellish, and the end result was that I migrated back
to Movable Type. What does that tell you? ‘Cuz it tell me a lot.) Anyway, I ramped myself up, got things ready, psyched myself for the process, got all hot n’ bothered. Then I ran across this article about migrating to WordPress 2.5
. Full stop.
I was reminded by that article of several very, very good points… and why I was using Movable Type in the first place.
Point 1. It uses static pages vs dynamic pages as the default setting. Why does this matter? Well, for SEO purposes it’s always better to have static pages, so there’s that. The links are cleaner. The code is cleaner. And above all else, there’s no database to eat shit when you most need it not to. The article offers an optimistic example… “when you’re on the home page of Reddit..” Right. Well, that’s not super likely. However, even a moderate hit on a shared database host could cause an outage, bump into some throttle, who knows. Why bother even finding out? Static pages FTW.
Point 2. So much of that WordPress functionality that I would find useful is built-in with Movable Type. Really basic stuff, just built right into the truly feature-packed Movable Type. The home page statistics, the asset management, the pinging tools. There’s lots to love.
Point 3. The interface. This point isn’t as terribly relevant as it used to be; the WordPress interface has improved significantly and there are many, many solid UI elements in WP that I’ve really got my eye on. The Movable Type interface is fantastic. I’ve loved it since the olden days, before all the fancy new improvements, but the newest iteration of MT is truly a thing of beauty. Side-by-side, WordPress feels… less than ideal. Again though, WordPress has its charm – and I appreciate the UI – but it really, truly isn’t MT.
Point 4. An interesting point in that it kind of works backwards. One of the ‘positive’ points for migrating to WordPress is that it is under really active development. There’s quite a bit of activity and that translates to ‘freshness’ to me… as new technology is developed (at that awesome pace it always is) plugins are developed, software is updated, etc. That being said, Movable Type is by no means a slouch… they’re just not as ridiculously fast to put it out there and let production sites Just Break. I can appreciate that. Besides, a few searches and I always turn up whatever plugin I could possibly need at the time from the Movable Type plugin repository
. That Just Works.
Point 5. Speaking of Just Works, Movable Type Just Works. So why in the world would I put myself through the inevitable pain and suffering that would ensue the moment I begin the process of migration?
I wouldn’t. I mean, if I didn’t stop to think about it, I might have. But as it stands I won’t do it. In fact, I was considering “Well, at least I can recommend WordPress to people who want something quick and easy to just put out there, right?” Sure, I guess I could do that. But wouldn’t it be better to recommend the Better Product? I think so, yeah.
So Movable Type stays on Jose Sierra dot Com. Thank you, Six Apart, for keeping me on the One True Path.