>Java? What does Go have in common with Java?
"Style" of it.
>Like I said, "practical"--that's how computers work.
No it isn't. CPUs now quite often have their own local memory so having explicit support for local arenas is becoming essential.
> What kind of cruft are you objecting to? make()? append() and friends?
The idiotic error handling with tuples. For example. Then the whole generics fiasco.
From what I'm seeing, a lot of Go code out there simply has no error handling - it either works or fails mysteriously.