Like, from the practical perspective, if you have a blog with content that is requested 1000 times per minute, but updates once per month (23 microtimes per minute), why on earth would you setup a database (with geo-redundant replica, of course) and run overly complex code to render the same HTML over and over every single time it's requested? The only possible answer here is being oblivious of other available options, and I believe author of the post is trying to raise awareness that there is another option.
That's not an excuse for terrible performance either way. At this point it's trivial to handle hundreds (or thousands) of req/s on common hardware if you just choose the right software to run.
You can you lamba/cloud functions as webhooks for your CMS to ping when a rebuild of the static site is necessary. Netlify helps you set this up easily.
Even if you updated a dozen times a day, it would take only a few minutes or less to rebuild and deploy.
edit: yes per-user data is a primary use case for dynamically rendered sites.
But public pages that all users load make sense as static if possible
That's what caching is for.
At times of panic you want to convey information as fast as possible and as efficiently as possible. Five nines availability.
What I take exception to is the idea that static pages are the one true way to achieve this goal, and TFA’s pronouncing that not using static pages is irresponsible.
Which means it was made into a static page. On the CDN. Wooo, progress!
That's not how a real audience works. If a web site overloaded, user will immediately skip to the next google result.
Moreover, “getting static” is nice and a fine way to improve performance, but it seems to me that really the goal should be, “be available.” What’s wrong with using a CMS or anything else as long as you have the capacity to meet demand?