A PHP file has less dependencies than a Go binary. There's over half a billion websites. There are probably under 20 million people in the world who know what a "static binary" is, fewer still who have the knowledge and resources to deploy one on the web. The vast majority of people with websites can use this PHP file as-is, with no additional learning or work -- just FTP it over to any penny host in the world. They'd not be able to do anything useful with a binary file.

I respectfully disagree. A PHP file may have lots of dependencies. And worse, these dependencies are mostly hidden. (Think of libraries used from within the PHP file). You can't tell if you have resolved all dependencies until you have fully tested all of the functionalities of a PHP file!

Anyway, since the code takes only 100 lines, this project could very well be written in any number of languages, I suppose.

Obligatory question, asking for an implementation in Brainfuck.

And what advantage would that give you? How are you going to run your Go static binary on a shared host without ssh access?

You are literally trying to nitpick on PHP's greatest strength, ease of deployment.

How about http://gohugo.io/ ?

Looks nice but when I click "Install" on home page of gohugo.io, I see: "brew install hugo". Another tool that I don't know: "brew", and that I probably cannot install on my shared hosting server.

The point of Void is minimalism: apache+php, nothing else required. < 100 lines of code in a single php file (+ the markdown parser lib of course).

Immediately above that it has a big button that says "Download", which takes you here (https://github.com/spf13/hugo/releases). Above the `brew install hugo` part, it asks "Using Homebrew?", implying that option is for people already using that tool.

I definitely agree that less complexity is better, but I think levelling that complaint against (this part of) Hugo is unfair.

Hugo is a static site generator much more fully featured than Void, so IMO its not fair to compare on LOC. As far as brew goes, that is just for convenience. You can might as well download the static binary from the releases page - https://github.com/spf13/hugo/releases

I believe the CMS should build on your local machine and then be pushed to your hosting after it builds the static files. Like Jekyl. That's how I'm reading it, and brew references Homebrew, an OSX package manager.

uhm... you don't need brew to install Hugo. It's an option.

How far along is hugo? I tried and failed to make the blog I wanted with it and had to hack around its deficiencies. I appreciate the fact that it's a single static binary, but its directory structure is overly complicated and arbitrary things don't work.