Discord have switched away from Go for some performance-critical services because of it. [0] https://discord.com/blog/why-discord-is-switching-from-go-to...
Go is fast enough for Google. It's too slow for you?
There's not a single proof except heartbleed in OpenSSL. I merely asked the author to provide the proof, not for you and I to engage in Go's memory safety and billions in damages and inherent nature of C and so on.
If we were to sum all the "damages" caused by faulty software, we'd arrive at a number that exceeds the total sum of money on planet Earth, let's not use that false metric for this discussion.
Is there an actual problem right now with nginx that Caddy circumvents with its architecture? Yes or no? That's the question.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0133
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2028
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-2089
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4315
Should I go on? None of the above errors is possible in a memory safe language like golang.