"I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.

I took a look at Rust awhile ago... but it just didn't look like a fun language to use. So I'm curious about why you find it more suitable than Go.

D is one of those languages that I keep meaning to poke at, but never get around to (because there's really nothing there except nicer syntax.)

As for Go:
I don't care for exceptions. Multiple returns with an error works well in my opinion.
I don't frequently use enumerations.
Generic types would be nice (or rather better polymorphism support in the same vein as Haskell's would be nice, but then again most of my complaints with Go end up being "well if it was more like Haskell...".)
CGO is certainly a weak point of Go's...
I have no great desire for dynamic linking, so I really don't care if only static linking is available by default.
I'm not a huge meta-programming fan... so the lack there isn't a big deal to me either.

To me, the nicest thing about Go is its standard library and documentation. I also like its clean syntax (for a C-like language.)