All is not sunshine and fruit punch in the world of WordPress. Using a blogging platform that is engineered like this one has a couple of drawbacks:
• Appeal to bad guys. Popularity and an open codebase are generally a good combination, but a few people out there are always looking to ruin everyone's fun. Because WordPress runs so many high-profile sites, some nefarious types are on the lookout for flaws that can be exploited. Luckily, the WordPress developers are very quick to patch vulnerabilities, but you have to stay on top of the releases.
• Dynamic page generation. WordPress dynamically generates most of the pages that you see. Each time you load a post, a bunch of things are happening in the background: Database queries are fired off, PHP code is executed, and then the page is displayed. Usually, this system isn't a problem; it ensures that the content of your blog is as up to date as possible. But this approach is a little more resource intensive than a static approach and can translate to your blog's being unavailable under heavy load.
Movable Type, the other blogging heavyweight, takes the opposite approach. Movable Type (MT for short) stores posts, comments, and the like in a database just like WordPress does, but it creates static HTML pages from that data. This arrangement makes MT a little leaner when serving up content, but publishing a post can take more time because each index page needs to be rebuilt. MT has added an option to use a dynamic system, but by default, it publishes static pages.
Was this article helpful?