Go doesn&#x27;t have the facilities that let you handle real-world concerns in a nice way. All the examples of bad, enterprisey Java - Spring AbstractSingletonProxyFactoryBean, XML config for everything, reflection-based JSON serialization, annotation-based transaction management, JavaSpaces - they weren&#x27;t written by idiots, they were written because they were the best way to solve real business problems within the limits of the language - limits that go also has.<p>People don&#x27;t like writing hundreds of lines of repetitive boilerplate the way go&#x27;s lack of generics forces you to. They&#x27;ll look for a better way, and they&#x27;ll come up with hacks, just as they did in Java.