For almost one week I have been setting up Blogial Networks and have played around with WordPress mu. I decided to use WPMU after trying out MovableType. I created a MT blog for FSLog and imported all the contents into it. With just about 350 posts, it created so many files for various views – single post, monthly archive, yearly archive, category view, etc. In total it took about 25 MB for all these files for just one blog.
Here are some of the basic reasons for not choosing MT and using WPMU:
- MT is huge. The zip file costs about 5MB and extracting it gets a 21MB monster out. Whereas WPMU is only 1.5MB – 6MB when extracted.
- Ease of use – during installation and for creating post.
- MovableType needs rebuilding so many files for every update to a single post. Missed out a word there, save it and republish the entire blog. This is unacceptable for a blog network which wants even technologically challenged people to blog. Not many would understand the republishing process (unless they are the old blogger type). I agree that plain html files are blazingly faster than executing more than 30 SQL queries for every request, but wp-cache does a great job in caching the rendered HTML pages in wordpress.
- Lot of plugins written in PHP. I can get my hands dirty with the plugins if I want to as I have seen and understood the WordPress architecture more than MT’s.
Regarding the last point, I would be running a series of posts about the various plugins that we use here are Blogial and the problems and incompatibilities we faced while installing it in WPMU.