Payday loans
Auto insurance

What’s in this Movable Type 3.0 thing after all?

I saw a few mentions around the Internet today that Movable Type 3.0 has been released. Most folks were whining about pricing, but I’m not one to complain about anyone charging any amount for software — if it’s worth the price, I’ll buy it, and if it isn’t, I won’t. (Oh, and I think most of the software I buy is far underpriced based on the frequency with which I use it, but that probably makes me rather weird.)

In other words, whether I use MT 3.0 is far more likely to be dependent on its feature set than its price. But what is the feature set? In the few minutes I’ve spent trying to find out, I simply can’t determine what it has that’s different from 2.6, why SixApart thinks I should upgrade, or anything like that. There’s a “full feature list” that doesn’t discuss what’s new in 3.0, a “product info” page that also doesn’t mention any of that, and no mention whatsoever about the new features or changes between versions other than licensing on either movabletype.org or sixapart.com. I understand that the licensing change is a big deal for Six Apart, but I’m a current user of your software who’s thinking about buying your new version. You gotta tell me why it’s what I want.

I’m well aware, of course, that I could figure out all of this with a bit of googling. The point, though, is that shouldn’t be necessary.

2 Comments

  1. Nathan Pearson Said,

    May 13, 2004 @ 11:52 pm

    This might be the page that you’re looking for: http://www.movabletype.org/help/#developer

    Off of developers, not the feature list. Which is a bit weird. There’s also a section on how to implement TypeKey in your own app, but it seems to mention registration and there’s nowhere else on typekey.com or moveabletype.org that seems mentions that. I’m guessing documentation is a work in progress.

  2. Eric Said,

    May 14, 2004 @ 12:00 am

    Yep…that looks a lot more like what I was expecting to see. Thanks! It’s still a bit weird, though. :)

RSS feed for comments on this post

google