You could edit JVM bytecode by hand, but nobody wants to, we have tools for that. I'm sorely tempted to make a language that transpiles to/from all the Go boilerplate that shouldn't concern human beings.
Some of the boilerplate is likely to go away in new versions. (See new "check" syntax.) But the hidden advantage of Go has always been the ability to look at a function and just see what it does. That comes at the expense of boilerplate, but is worth it.
Whenever I look at some Go, it seems the "what it does" is buried in a big pile of mechanics that could have been generated. You're more likely to see half a dozen error-prone lines copying between slices than an obvious HOF named "filter".
Can you give me examples of what you mean? I agree some of it is low level, verbose even, but on the other hand, I'm able to figure things out on new projects rather easy, there's just fewer layers and magic things happening.
