With ~a week of exposure, I can answer this better now:
Quote:
Originally Posted by Wolfram
How are you enjoying Go?
The language seems pretty nice and packs a lot of power into a relatively simple package, coming from C++. Goroutines and channels are very nice features to have built in and I'm looking forward to gaining a better grasp on how to use them effectively.
Downside: hate the package system. It has very strong opinions about how your workspace should be set up, and the notion that you have to include every other package (including stuff you write) with what is essentially an absolute pathname seems bad. You can move C++ code around and change your project's include path, but if you move Go code around...everything breaks? I imagine (hope?) there's safeguards around this sort of thing because it's so obvious, it just seems really counter-intuitive.
Quote:
Originally Posted by Wolfram
The language spec is really simple and short, so people advocate reading the complete thing. Not something you'd do for other languages.
One of my coworkers told me this as well, so I tried and wasn't really feeling it. When you're like "I want to learn about this sexy channel stuff" it's kinda painful to read through all the grammatical forms of defining a struct or whatever. I quickly moved on to
A Tour of Go to learn the basics through some examples and exercises, and I think maybe now I'm more prepared to go read through the spec.