Are you kidding me? This post is so full of arrogance and brazen oversimplifications of both Java and Go, there is so little of actual value to even bother discussing.
It's almost like you don't realize that Java came out a decade before Go, or that you don't understand the power of Goroutines or the power of writing your own low-level concurrent code.
I'd hate for you to find out that java's concurrency primitives are probably implemented using the same constructs as goroutines and/or are available to devs in the sync package. (Feel free to write "thread"-safe data structures. Hell, if you'd wanted to complain about the lack of generics in that case, I'd have even joined you.)
Research, sure, but it doesn't ignore the last decade of practical experience writing programs. A programming language is a user interface. The theory isn't all that matters.
And yet I'm writing tons of code in it very quickly. I don't know how it missed HN, but Go also now powers Google's download infrastructure (Chrome, etc)
It's almost like you don't realize that Java came out a decade before Go, or that you don't understand the power of Goroutines or the power of writing your own low-level concurrent code.
I'd hate for you to find out that java's concurrency primitives are probably implemented using the same constructs as goroutines and/or are available to devs in the sync package. (Feel free to write "thread"-safe data structures. Hell, if you'd wanted to complain about the lack of generics in that case, I'd have even joined you.)