True, yet I tend to read the specs, (bundled) libraries and compiler design docs of the languages I use, because I don't like to fly blind, if you pardon the term.
I didn't advance into stdlib and compiler yet (I'm a beginner in Go, I may say), but its behavior didn't disappoint me yet, and the specs make sense.
I have a couple of multithreaded tools on the roadmap, which will help me understand the gopher better.
True. But writing short critical posts on HN isn't the same as understanding the language, either. Why should we believe your opinion on the language to be more correct than bayindirh's?
Frankly, you sound like a zealot, and I distrust zealots in the area of computer language design. (I distrust them in a lot of other areas, too.) I trust pragmatists a lot more.
You've shown off a decent vocabulary, but there's far more rant than substance. Got any substance to show us why we should listen to your opinion?
