[ohashi]

What doesn't make sense about it?

I can see a lot of scenarios where you start with a CMS because it does a good job of doing what you need. Why reinvent the wheel?

Scaling issues is going to occur in all code, even code you write and know inside and out. It just means you become entirely responsible for debugging and re-architecting to improve its performance.

@Drupal specific comment, you could easily throw nginx as a reverse proxy with a cache in front if everything is static and be done with it.

[typicalrunt]

Valid point. What I keyed on in the article is that it is a complex install, and that tells me that maybe his CMS is working against him. In those cases I like to remove the impediment and simplify the data model (which should simplify the code).

[ohashi]

I can't comment on the specifics but he said it was something default in the comments table and modules I think. For a big project like wordpress, I would try to understand why a certain decision was made. Try to understand the consequences of that decision vis-a-vis how I would want/expect it to work.

[druiid]

Doesn't even have to be static to put nginx in front of it! As long as you can set proper cache headers from your script (in this case Drupal, and I imagine it does), you can cache even dynamic-ish sites quite well!