I've had a site running on MT for the past two years, with nearly a year's worth of Blogger entries before that. About 4,000 individual entries and over 6,000 comments dating back over three years. One would think that migrating a site of that size would be a royal pain in the ass.
WordPress imported the whole thing in a matter of minutes. It's easier to upgrade from MT2.6 to WordPress than it is from MT 2.6 to MT 3.0.
WordPress is fortunate to have hit its stride just as the MT licensing brewhaha was hitting. WP 1.2 has all the features of MT, runs faster, and is completely open source and GPL licensed. It's a bit of a paradigm shift from MT - you have to get used to a dynamically-run system rather than static templates, but once you grasp the power it brings it offers a lot of new potential for blog development. Plus, there are a lot of talented hackers who have been turned off by MT licensing and will be developing WP plugins instead. WP even has features that MT doesn't - for instance automated link management. That alone makes it worth the upgrade.
Plus, future versions will support multiple blogs under one interface, some more commenting controls, and other features. I'd expect as WordPress captures marketshare the development of new core features and plugins will increase as well.
That's a big selling point - even if the WP developers wanted to pull the rug out under free users like Six Apart did, they couldn't. WordPress is GPL software, meaning freedom is but a fork away. Mark Pilgrim's piece does an excellent job of detailing why that freedom is so important. It's another reminder of why open source software is better than proprietary software in terms of flexibility and licensing.
Personally, I think anyone that plays around with WordPress will eventually see how much better it is than MovableType and just switch... I did a short while ago and can't even think of ever going back.
I don't really want to run MySQL. I don't really want to maintain it. It is just not something I want to deal with. MT lets me use a little local database.
I really really don't want dynamic pages. I just don't need it. I have had zdnet link to my blog which caused a trillion avantgo clients to hit it. I just don't need queries to MySQL and PHP being run all the time. Actually PHP by itself wouldn't be so bad if it cached everything in a local file the first time the page required it as long as it supported if-modified-since and ranges correctly.
I actually kind of like the idea of TypeKey. Of course nothing prevents you from implementing TypeKey support in WordPress.
I simply don't care about silly licensing issues. I mean, for a single non-commercial blog, nothing has changed.
I have an upgrade path. Sooner or later WordPress will probably integrate a local databse and real caching. When that happens if it is better than MT, I'll migrate. I just don't see the point in migrating right now.
I've been using Project Steve Guttenberg [projectste...enberg.org] primarily because it was the only one I could find at the time that didn't require a database backend' my 486 which was fine for serving static webpages just couldn't handle that load. I never did find any others that did not require a database of some sort. I don't see the need for it when it's just a personal weblog. A site like/. of course needs one, but when I'm posting maybe 10-15 posts/month, and very few people are looking in the archives, it just didn't see
At the beginning there was a "classy blogtool" called b2 [cafelog.com].
When Michel V., the original author of b2, stopped development of his tool, two forks emerged simultaneously: b2evolution [b2evolution.net] and WordPress [wordpress.org].
This was in early 2003. For some reason, Michel V. later chose to endorse [cafelog.com] the WordPress fork as an "official" successor to his work.
Anyway, both forks have developped at approximately the same pace but with slighlty different orientations. b2evolution is merely moving towards a larger scale multilingual multius
The time spent on any item of the agenda [of a finance committee] will be
in inverse proportion to the sum involved.
-- C.N. Parkinson
Why WordPress Is Poised To Take Over (Score:5, Insightful)
I've had a site running on MT for the past two years, with nearly a year's worth of Blogger entries before that. About 4,000 individual entries and over 6,000 comments dating back over three years. One would think that migrating a site of that size would be a royal pain in the ass.
WordPress imported the whole thing in a matter of minutes. It's easier to upgrade from MT2.6 to WordPress than it is from MT 2.6 to MT 3.0.
WordPress is fortunate to have hit its stride just as the MT licensing brewhaha was hitting. WP 1.2 has all the features of MT, runs faster, and is completely open source and GPL licensed. It's a bit of a paradigm shift from MT - you have to get used to a dynamically-run system rather than static templates, but once you grasp the power it brings it offers a lot of new potential for blog development. Plus, there are a lot of talented hackers who have been turned off by MT licensing and will be developing WP plugins instead. WP even has features that MT doesn't - for instance automated link management. That alone makes it worth the upgrade.
Plus, future versions will support multiple blogs under one interface, some more commenting controls, and other features. I'd expect as WordPress captures marketshare the development of new core features and plugins will increase as well.
That's a big selling point - even if the WP developers wanted to pull the rug out under free users like Six Apart did, they couldn't. WordPress is GPL software, meaning freedom is but a fork away. Mark Pilgrim's piece does an excellent job of detailing why that freedom is so important. It's another reminder of why open source software is better than proprietary software in terms of flexibility and licensing.
Re:Why WordPress Is Poised To Take Over (Score:1)
Re:Why WordPress Is Poised To Take Over (Score:2)
It can be found here:
http://diveintomark.org/archives/2004/05/14/freed
Re:Why WordPress Is Poised To Take Over (Score:1)
Re:Why WordPress Is Poised To Take Over (Score:1)
I like the sub-categories and the admin interface is a whole lot cleaner than MT.
Re:Why WordPress Is Poised To Take Over (Score:1)
Re:Why WordPress Is Poised To Take Over (Score:4, Interesting)
I don't really want to run MySQL. I don't really want to maintain it. It is just not something I want to deal with. MT lets me use a little local database.
I really really don't want dynamic pages. I just don't need it. I have had zdnet link to my blog which caused a trillion avantgo clients to hit it. I just don't need queries to MySQL and PHP being run all the time. Actually PHP by itself wouldn't be so bad if it cached everything in a local file the first time the page required it as long as it supported if-modified-since and ranges correctly.
I actually kind of like the idea of TypeKey. Of course nothing prevents you from implementing TypeKey support in WordPress.
I simply don't care about silly licensing issues. I mean, for a single non-commercial blog, nothing has changed.
I have an upgrade path. Sooner or later WordPress will probably integrate a local databse and real caching. When that happens if it is better than MT, I'll migrate. I just don't see the point in migrating right now.
Project Steve Guttenberg (Score:1)
I never did find any others that did not require a database of some sort. I don't see the need for it when it's just a personal weblog. A site like
Re:Why WordPress Is Poised To Take Over (Score:1)
At the beginning there was a "classy blogtool" called b2 [cafelog.com].
When Michel V., the original author of b2, stopped development of his tool, two forks emerged simultaneously: b2evolution [b2evolution.net] and WordPress [wordpress.org].
This was in early 2003. For some reason, Michel V. later chose to endorse [cafelog.com] the WordPress fork as an "official" successor to his work.
Anyway, both forks have developped at approximately the same pace but with slighlty different orientations. b2evolution is merely moving towards a larger scale multilingual multius