> But all the inconsistencies in the language design have made learning it feel like a chore. That's interesting. Go is one of only two languages that I've bee

> But all the inconsistencies in the language design have made learning it feel like a chore. That's interesting. Go is one of only two languages that I've been able to learn by writing production code without feeling like I'm getting "held back" by my inexperience (or, on the flip side, holding others back). It never felt like a chore to me; there was only one "gotcha" that caused me a significant amount of frustration. > So what’s the response from Go’s designers about the requests for nullable strings? To treat the empty string as a special value. Sometimes it’s like they haven’t even read their own design justifications. The only time I've run across this is with JSON encoding/decoding, but there's a really easy solution to this (take a look at gobson, for example[1]) [1] http://labix.org/gobson http://labix.org/gobson