A static site resembles good stonework. Once assembled carefully, it tends to remain stable for years with surprisingly little maintenance.
Complexity has a carrying cost
Every runtime dependency becomes a small living creature that must be fed, patched, secured, monitored, and eventually migrated.
Static architecture avoids entire categories of operational exhaustion.
Dynamic where necessary
This does not mean avoiding dynamic systems completely. It means placing them carefully.
Public content, documentation, philosophy pages, and blogs often work beautifully as generated static assets. APIs can remain separate and focused.
The public web should stay light
A fast static page respects both the user's time and the planet's electricity bill.