Seems to be a lot of drama around dep. I don't like the way that rsc handled that situation at all (he would have been better not pretending to consult, and not trying to bring dep into the fold as a semi-official experiment). Calling it an official experiment and holding meetings with Sam made it seem like there would be significant input from the dep team, but that never happened. So lessons to learn for everyone, but give the structure of the Go team and Russ's place in it, it seems unlikely dep has a significant future.
Not sure I understand the need for this - if you are using containers it should be for instances which can die and you don't care what happens to them after. People sometimes put stuff in containers that they shouldn't (document storage, databases), which would be better hand-managed or using a central service for.
Definitely think the way the Go developers think about versioning is very different from the way others tend to use it.
What sets you apart from other freelancing shops?
JWT is a bit of a minefield, not sure I'd recommend using it.
TLDR: Garbage collection caused pauses
See also https://speakerdeck.com/andrestc/understanding-go-memory-allocation-gophercon-uk
Sounds like a very minor release for a bug fix
Seems to be a lot of drama around dep. I don't like the way that rsc handled that situation at all (he would have been better not pretending to consult, and not trying to bring dep into the fold as a semi-official experiment). Calling it an official experiment and holding meetings with Sam made it seem like there would be significant input from the dep team, but that never happened. So lessons to learn for everyone, but give the structure of the Go team and Russ's place in it, it seems unlikely dep has a significant future.
This is a little thin - might be better as a blog post explaining what it is doing and why you use it?
Not sure I understand the need for this - if you are using containers it should be for instances which can die and you don't care what happens to them after. People sometimes put stuff in containers that they shouldn't (document storage, databases), which would be better hand-managed or using a central service for.