Thanks for dropping by. I have used both MT and WordPress. I like them both. The MT rebuild process kills me everytime. Don’t be a stranger!

There have been disappointingly few reponses, and those boil down to “it depends”, which is not at all helpful.

I suspect you are correct that MT’s Perl/CGI architecture places a greater burden on the server. After all, unless it’s runing under mod_prel of FastCGI, MT launches another instance of Perl every time it hits one of those CGI scripts. (That’s the reason all those MT sites were killing servers in 2004 when the comments spammers went after them. Each comment triggered a new Perl instance.)

That’s not MT’s fault, though. It’s Perl’s fault. It made sense for Ben Trott to write MT in Perl because you could count on hosts running Perl back then, but not PHP. Times change. These days, Perl is like the strange old aunt you hope doesn’t come to your birthday party. I’d like to see Six Apart retain MT’s template structure, rewrite the engine in something more contemporary, and then release the Perl code as open source. If they were clever, existing MT users could upgrade to the new engine without much hassle.

On the other hand, tools like WP may be easier on the server, but I’m not sure they’re easier on the reader. Nothing is served faster than a static HTML page.

It looks like I’ll go with a WP installation this time, if for no other reason than to avoid the need to rebuild the entire site every time you make a design change under MT.