I don't really understand the point of that article.
There are three institutions mentioned: 1. The Go project, 2. Microsoft and 3. Antivirus vendors.
- From what I can tell, the Go project isn't involved at all - at least if the author of the article is correct (I can't test that) in that this issue happens with all statically compiled binaries, it affects every piece of software built that way. That's not really unique to Go.
- Microsoft is involved insofar as they are an Antivirus vendor as well, with Windows Defender. But apart from that…
- The Antivirus vendors, of course, are who have to fix their products.
The article suggests the root cause of the problem is a lack of communication between the Go project and the Antivirus vendors - the entity who has ~nothing to do with the problem and the entity who has little to do with it. That seems a very strange argument to me.
Of course, the Go project and Microsoft might work together on some sort of initiative to convince the Antivirus vendors to fix their products. I'm not opposed to that. But it really feels to me, that this is barking up the wrong tree - the author should really only point the finger at Antivirus vendors. They are who's at fault and they are the only ones who can realistically fix it.