Thank you for your condescending reply. I understand Go's memory model quite well (and have used Go quite a bit). News flash: you can have bugs of other kinds besides buffer overflows.
Er, sorry, I wasn't being condescending. I intended to clarify some relevant facts, please don't take it personally.
You had said:
> Go's memory safety isn't some kind of automatic security guarantee...
But in some cases, it is. I'm not claiming more than that, nor am I saying that you can't have "bugs of other kinds" -- on which point I agree with you.
> Er, sorry, I wasn't being condescending. I intended to clarify some relevant facts, please don't take it personally.
Fair enough, it's easy to misunderstand the intended tone in online comments.
You don't have to run Caddy as root in production, even to bind to low ports. (None of my sites do.) https://memorysafety.fail for more info on memory unsafety.