The only logical explanation I can think of based on my personal experience is that shared hosting services offer Apache web server by default so they can host WordPress websites which by the way, based on w3techs.com, 43.1% of all websites are WordPress.
You may ask why Apache then? Well, because when a user modify some settings via dashboard, they change in .htaccess which does not expect a web server restart or super user permissions like you need with NGINX, for example.
Now you know why WordPress websites are getting hacked easier than other CMS-es...because they can apply changes in .htaccess on the fly, whereas with other web servers, you need root permissions, thus the extra layer of security.
I have tried to follow Hugo's development but lost track with its constant evolution and addition of features I do not need...therefore for now I follow a simpler path: I keep my data in markdown files and I plan to switch to asciidoctor for good; it's quite old, it's battle-tested, and offers me many options to produce various forms of output; be it HTML, PDF, ePub, etc...
If O'Reilly trusts it to produce its ebooks, then I'm sure it worthy of my time and effort!
There is an April Fools' joke [1] that demonstrate this and I cannot tell it's readable or not...I personally find it confusing in Python, but not in C's case which can make things clearer, if you use it wisely and in moderation!
The first thing I thought when I read this weird article was "wait...do they use their database synchronously in an asynchronous environment or am I missing something here?".
Most of us have been bitten by this naive mistake and I'm sure we have learned our lesson.