@natty @ezio Also #GCCGO is not compatible with Caddy so for now it isn't usable.

The Google-pwn'd toolchain is no good.

@bronger That is true. For now there's #GCCGo which unfortunately lags behind, but I still think it's a sign of an ecosystem with ailing health.

For now I simply cannot replace those programs so I can only remain vigilant that nothing unwanted sneaks in despite demonstrated intent to have such.

@krom For now. When fundamental parts of the stack start getting attacked in such a way, there's cause to be concerned that it will spread.

Like I highlighted in other posts, #GCCGo is subject to none of these issues, but it's also a second-class citizen in the #Golang ecosystem.

@liw @joeyh @be In the meantime there's #GCCGO but essentially this has me considering #Golang software legacy to a greater extent than unmaintained #Pascal.

The major driving body for the language and its tooling's design is overtly malicious. Shifting away recommended if it wasn't already done.

#Golang #GCCGolang

@locnar @nixCraft Thank goodness we have #GCCGO and #DiverseDoubleCompiling.

#Golang

@jssfr Sure is a shame so few people paid attention to #GCC #Golang...

It was pretty much a foregone conclusion that a #Google-controlled technology (if more in mindshare than direct authority) would enshittify itself eventually.

#Go #GCCGo #GCCGolang