Is Go forkable (for lack of a better word)? That's the only question that comes to mind when I read the article. You have the source code, and this shouldn't be a difficult change to make, so I think "fork-and-fix and see who follows along" should be the mentality to practice in this case.
If you want to implement strings.Compare better, you can write a package and publish it for other folks to import. The function is not particularly special.
"The only sure path to failure is to not even try."
Or are you both implying the power of and supporting the massive monopoly that Google already has?
This is not a reasonable assessment.
Golang is massive; why would anyone switch to not-Golang which isn't backed by a large organisation and just has one string comparison optimisation?
And why would anyone trust a forking entity that forked a runtime to make a change that could be packaged as a library, as the comment you're replying to already suggests?