I'm not seeing the point here, TBH. What use-case does this author's single-binary satisfy?

1. You just want to serve static files from your blog? Install a webserver and knock yourself out in your editor, creating html and css (and maybe js) files.

2. You want to serve static files, with some dynamic crap stuffed inside here and there like the examples given in the article? Install the mod_php or equivalent for your webserver, and go mad with the editor.

3. You want fully generated content? Install one of the many backend frameworks in any language you want to use, and then go mad in your IDE.

What use-case does "one binary I wrote in Go" satisfy that isn't covered above? From everything I gleaned from the article, the PHP solution is even easier, while still technically being "one single binary".

EDIT: as an example of over-engineering, here is the authors code for a specific use-case:

    func ipHandler(w http.ResponseWriter, r *http.Request) {
     w.Header().Set("Content-Type", "text/plain")
     fmt.Fprintf(w, r.Header.Get("X-Forwarded-For")+"\n")
    }
    ...
    http.HandleFunc("/ip", ipHandler)

And here is the equivalent in PHP:

    header('Content-Type: text/plain');
    echo $_SERVER['REMOTE_ADDR'];