I would tend to agree, and yet there is something intellectually challenging about learning something new! I've been on the c# bandwagon since 2004; assembly and C before that. Go brings back some of that low(er) level feeling :)
I could tell you some horror stories about how my current employer does C#. It is very strange.... can't use var, nuget packages for _every_ class library... and it gets stranger from there on out... unfun!
Honestly, this is a good argument and it should not even be made here but rather when discussing dire and completely self-inflicted state of affairs that a lot of products written with C# are in. It's not just that "the product you see no reason to rewrite in .NET 8" causes talent attrition. It's that it causes that said talent to leave .NET altogether, despite the fact that for greenfield products it's much better at 85% tasks being usually thrown at Go. It's an unfortunate predicament.
I could tell you some horror stories about how my current employer does C#. It is very strange.... can't use var, nuget packages for _every_ class library... and it gets stranger from there on out... unfun!