Not sure about this one - seems to be a lot of logging and testing packages there, but that's just because everyone does those things, and many people reach for a library to help them test after coming from other languages which required it. Personally I find the built-in testing absolutely fine with table driven tests, sub-tests, I don't feel the need for things like assertions (that's what if is for !).
The logging is more interesting - perhaps a case there for structured logging in the standard library.
Hmm, not sure what this adds above caddy for example? It is simpler I guess.
Good article.
Wow, that was a deep dive, not what I expected at all, but really interesting, thanks.
Not sure about this one - seems to be a lot of logging and testing packages there, but that's just because everyone does those things, and many people reach for a library to help them test after coming from other languages which required it. Personally I find the built-in testing absolutely fine with table driven tests, sub-tests, I don't feel the need for things like assertions (that's what if is for !).
The logging is more interesting - perhaps a case there for structured logging in the standard library.
Slice sorting is in there at last! https://github.com/golang/go/issues/16721
But what does go bug do, it's not really explained in the slides?
heh, great to see these screencasts with a real game being built, rather than abstract examples. Keep at it francesc!