[pacemkr]

What parts of Wordpress do you find superior to alternatives?

I'm building yet another blogging platform (not quite) right now. It isn't going to be Wordpress, but it will be managed and won't cost you $200/mo. A carcycle, if you will.

To carry the analogy to its end: you seem to be only using the car to drive ten blocks to work. In other words, you only serve static content + comments. Which is why I'm curious what, specifically, compels you to stick with Wordpress even though there is an obvious cost (be it money or effort.)

[patio11]

The biggest one is the ecosystem. Can I get a WooThemes-caliber theme done for your CMS at 3 AM in the morning for $70 without talking to anyone? And will it work virtually instantly as soon as I drop it over? And will that play well with e.g. using the blog as a lightweight CMS, with custom menus, static pages, and whatnot in addition to the blog proper? And will that work with the plugin ecosystem when I want to do just-a-wee-bit-trickier things like the What Would Seth Godin Do prompt?

[pavel_lishin]

> Can I get a WooThemes-caliber theme done for your CMS at 3 AM in the morning for $70 without talking to anyone?

I know you run a business, so for you the answer may be 'yes', but for most people running a blog: is this really a huge concern?

To borrow an upthread analogy, if I'm switching from a car to a bike, whether I'll be able to get a complete paintjob at 3am for $70 without talking to someone is not really something that's going to make the pros/cons list.

[tptacek]

I think compatibility WooThemes & friends is, in fact, a huge concern for the majority of bloggers.

[gridspy]

Perhaps not those with traffic problems. Hopefully by then you've found a way to direct that traffic to useful revenue or have enough cash from your business to invest.

In OP's case, he's spending money on hosting a CPU-intensive blogging engine. In theory he could spend the same money on theming an efficient one.