Just don’t use Microsoft garbage wherever possible. Default opt-in is how it starts.

> Just don’t use Microsoft garbage wherever possible. Default opt-in is how it starts.

You don’t know what you’re talking about.

This fork is for use internally within Microsoft, and consists of patches which allow them to build FIPS 140-2 compliant applications using Go. Their stated goal is to get their changes merged upstream.

It’s not intended for use outside of Microsoft, it doesn’t support most of the platforms that Google’s Go does, and it isn’t meant to replace Google’s Go for any single person outside of Microsoft, though I suppose it would be useful for anyone wanting to write FIPS-140 compliant Go applications.

It’s open source, so you can check it out and compare against google/go if you want. It’s microsoft/go on GitHub.

You make all anti-Microsoft people look insane then you make statements like this from a position of ignorance.

Will it be used in Visual Studio?

Will it be used in any build tools on Azure?

It’s used for infrastructure stuff within Azure, I think. Probably other stuff, too.

Why would it go into Visual Studio? Go isn’t in Visual Studio now. I don’t see that changing. What build tools in Azure are you referring to?

Not just Microsoft,avoid all big corporates.

What is the Microsoft build of Go even for?

Historically, FIPS 140-2 compliance. However I believe mainline Go 1.24 is now going through validation for FIPS 140-3 compliance for crypto in the standard library.