Ehh I agree with you but I also haven't seen an "actual" exploit for a go memory corruption vulnerability outside of POCs.

Like I know it's possible with effort and maybe it was just lack of interest or adoption (like lets be fair its not a browser writing or pdf rendering engine type of language...) so while that situation was not great it never struck me as a burning problem with practical impact in the ecosystem either.

Interested in any pointers if possible.