Though if it is really never going to become more than just a blog, I choose static files with a simple compilation procedure, personally.
Moreover, I'm not sure where your disagreement with OP is, since you're simply saying now that for a given set of criteria, a superior choice exists. Which was the message in the first place.
And this is where I agree with you completely. You can't say that because someone is making a blog they must use WP as it is the correct choice. You can say 'I believe WP will be the correct choice in making a blog but Your Mileage May Vary depending on what you want to do with the blog and if you are more proficient in Ruby than in PHP.
This is exactly my argument, as the OP says you can't do this kind of thing and need to give a concrete solution. However, this kind of thing is incredibly necessary, and saying to use WP for every blog is just wrong.
What's better for making a blog? Tweaking a PHP wordpress theme or making something using Ruby on Rails? Your Mileage May Vary ?
The reason that term is used a lot is because there is a huge amount of evidence that each technology choice usually has very specific project criteria in which it shines, and if you change the criteria even a little bit, there is often a technically better choice - let alone a new technology that could be developed specifically for those new criteria.