(This post is part of a series on why Movable Type is an excellent choice as both a CMS and a blog engine. This is the introduction. The next post is Myths, FUD and reality about Movable Type)
Following the news that Six Apart is no more, many people—among which the vast majority isn't even using any Six Apart product today—are speculating about the death of Movable Type. Not only Movable Type isn't dead, it is under active development, and I would like to explain why the Movable Type publishing platform remains an excellent solution, both as a blog engine and as a web content management system.
I have been using Movable Type since 2002 (I paid for my copy of this "shareware" when it was just Ben and Mena Trott in their proverbial garage). I now make a significant part of my income thanks to Movable Type, and most of my clients using it. I also interviewed at Six Apart US for the job of Movable Type Product Manager, but it didn't pan out. I am therefore biased, but a few things save me from being oblivious to reality.
Firstly I'm the kind of consultant who'd lose sleep over giving a bad advice to a client, and the kind of engineer who'd lose sleep over delivering something based on an irrelevant or dead-end technology. I do not shove new technologies on clients because they're fun to play with, or simply popular; I do not make choices lightly or on a whim, but after a careful look at the bigger picture.
Secondly, would Six Apart completely disappear tomorrow morning (they haven't, more on that later), none of my clients would be impacted (neither myself for that matter). The MT code is long-lived, rock-solid, secure and there is a small army of experts who are capable of hacking it at will whether its original editor remains in business or not.
In this series of posts I will address the following points:
- Myths, FUD and reality about Movable Type
- The Movable Type Communities
- The Movable Type Platform
- The rationales for using Movable Type
(This is a work in progress, please stay tuned and pardon the occasional edit.)