And your proof is?
> golang is worse for large teams and maintainability compared to languages like Java and C#
How do you figure that? I see large projects like Kubernetes and Docker thriving with contributions.
> Which ended up complicating end users' code.
Some users, sure. Majority of projects, as evident in Go annual surveys clearly shows they are doing OK without it.
> ended up with a weak language
Looks strong to me!
Years of experience working on several large golang projects, and seeing what sorts of issues and bugs programmer face when working on them. Things that they wouldn't have encountered in Java or C# for instance.
Furthermore, the burden of proof is on the golang authors making the claim. I have not seen any rigorous studies that underly the design decisions they claim will result in more maintainable large code bases.
> How do you figure that? I see large projects like Kubernetes and Docker thriving with contributions.
That's despite of golang, not because of it. C is quite bad for large scale projects, yet Linux has a lot of contributions because it is a large project (a tautology of sort).
> Some users, sure. Majority of projects, as evident in Go annual surveys clearly shows they are doing OK without it.
A biased survey that mostly pro golang people would take anyway.
> Looks strong to me!
See first point.
ok - I was gonna run some BigQuery and get you stats - but that comment makes it clear as day that you're not interested in "proof".
Thanks for saving me time and good luck to you and your Java/C#.