Fair points, but I still think any consideration in language choice is affected by documentation. I frequently see this as an obstacle in older languages. E.g. when writing Python code one will get tripped up a lot by the 2.x to 3.x transition.

C# has also gone through a profound number of changes which means the internet is littered with old obsolete code and way of doing things. This makes training new C# developers harder.

Especially since Microsoft itself cannot even get it right. Keep in mind the whole point of my article was to compare EASE OF USE. The confusion imposed by all the features, recent changes and conflicting documentation around C#, certaily does not give it extra points on usability.

I think this is an area Go has a remarkable advantage. The language is almost unchanged in 8 years. I can pick up Go books which has been in my shelf for years and use the code examples there and they work just as well today.

Many year old blog posts or Go are still relevant.

Btw C# is not alone with this problem. As former iOS developer and Apple fan, I was a big fan of Swift. But I think Swift has developed many of the same problems as Java and C#. There has simply been such a rapid evolution of the language, that quite a lot of old code and ways of doing things are no longer relevant. The complexity also get difficult to deal with.

And Swift is still a simpler language than C# and Java., as it got a lot more things right upon first release without the need to artificially bolt on lots of stuff afterwards like C# and Java.