Of course, your concern is valid: I don't think anyone recommends using a static content generator except for sites that consist primarily of static content. Obviously if you want richly dynamic content, a static site generator is not for you. On the other hand, if your site is primarily static, why use a dynamic system that introduces additional overhead?
Then, most of time, they end up spending an awful lot of time with the wordpress export/import tools (which is made even worse once you starting using payed plugins). Which sometimes involves looking at random php errors.
Compare that with copy / pasting a bunch of file via ftp, and then you're done.
and it works for backups too...
And conflating "interesting" with "dynamic" is rather dubious to me as well.
Why do they think they need dynamic pages? The upsides of dynamic pages (no more waiting for pages to rebuild) are right there in their face, while the downsides (your server falling over if you get more than three readers at a time) don't become evident for a while. So to non-technical folks, dynamic pages seems like a no-brainer. They don't learn the downsides until they leap up and bite them.
This mismatch between what people think they want and what they actually really should want based on their needs is sadly quite common in tech products, and explains how a lot of crappy products managed to become more popular than a techie would ever have expected them to be.
For someone writing a personal blog, who wants a minimal attack surface and minimal resource usage per hit on any access pattern (not just the easily cacheable ones), with minimal hassle, Pelican and its friends can suit quite well. I ran Wordpress for years and years. I got tired of hearing about a new zero-day total-compromise exploit forcing me to upgrade every week. I got tired of tweaking Varnish or any other caching solution all the time, and none of them ever getting proper ETag/If-None-Since behavior. If I needed a full-fledged "product" solution I might have moved up to something like Drupal or Django. Instead I moved down to Pelican. Maintaining my 14-year-old blog is just less annoying now.
Wordpress is simple, but not low-maintenance. It's an important distinction. Most programmers, and I think most writers too, don't need an idiot-friendly UI so much as they need something that Just Works and Just Keeps Working.
Interestingly, his first reason / argument to switch was about having the content locally and being able to use markdown.
I like the idea of storing the content in an version control system. I think it would be great for sites like gwern.com.
But still: if you don't have much content you will get speed and security practicality for free.