C# only happened in the Microsoft part of the universe for most of its life. Java has a bad reputation because its community appears to favor over-engineered o

C# only happened in the Microsoft part of the universe for most of its life. Java has a bad reputation because its community appears to favor over-engineered opaque solutions (that whole ProxyAdapterFactorySingletons business). Go pushes a quite different style, favoring explicit bindings over dependency injection. Disclaimer: I write a lot of Go, but I don't have productive experience with C# or Java, except for a semester-long project at university where Spring Boot was mandated. I recall most students having trouble with its implicitness, i.e. they could not build a mental model for why certain changes had certain effects.