> Then you just pre-build the page before publishing it.

That's "using a programming language to solve the problem", isn't it?

> It's way cheaper as you do the work once, instead of every client being much slower because they have to do additional requests.

What work do client-side includes have to do other than fetching the page (which will get cached anyway)? It's less work to have a `<include-remote ...>` builtin than even a simple Makefile on the server.

An additional requests for html isn’t slow, and now I have to have a whole “build” process for something that is basically static. Not ideal