The scripts could be adapted to work without requiring URL rewriting on the server.
The second complaint is about styling which currently doesn't seem possible. If you're a project of any considerable size, you probably will want your docs to be branded in some way which is not possible either ATM.
I think it is a fair criticism to point out that the author seems unhappy about a non-OS website yet they somehow think this is an OS issue.
The problem is that DocC is incompatible with the current tools that many Open Source projects use.
Sure, you could use DocC for an OS project and set up your own server to host it. It's probably pretty cheap to do that on a VM. It would require just a little bit of learning about web hosting and would require minimal maintenance.
But why would anyone do that when Github pages is completely free, requires zero maintenance, and everyone knows how to use it already?
A lot of small Open Source projects currently use Github + Github pages for hosting docs because it is such a convenient offering. If you want to use DocC, you have to look for something else.
As far as I can tell, that’s not true. The output is completely static and just requires some very basic URL rewrites.
The Netlify config in the linked blog post (https://josephduffy.co.uk/posts/hosting-docc-archives) illustrates this quite nicely. While Netlify has some Function-as-a-service capabilities DocC uses none of that.
My understanding of static webpages is that there's zero processing happening server-side. "Basic URL rewrites" counts as processing in my book
I personally even disagree with that architecture, I think it’d be better to pretender the content for all pages (like, e.g., Gatsby does) but I wouldn’t call it not a static page.