I've posted it because I'm always on the lookout for simple solutions for complex problems, and especially for how these solutions are designed. The post describes the design process well.
Also Rob Pike is a great technical writer. Another example of his style is "Effective Go":
yup, and if people are looking for usage I just found a gist that shows how gob handling can be useful (writing to cache that allows the reading back to be castable into the correct structs) https://gist.github.com/pioz/ca5b7a11200f54afbd76dee7acbcc06...
It's an entirely reasonable question to ask "is there any specific as to why this is being posted today?". If the answer is no, that's fine, but there may be extra context that is interesting and not obvious.
Comments
this is quite old, so I'm curious about what triggered it being posted again, has something happened / changed?
I've posted it because I'm always on the lookout for simple solutions for complex problems, and especially for how these solutions are designed. The post describes the design process well.
Also Rob Pike is a great technical writer. Another example of his style is "Effective Go":
https://go.dev/doc/effective_go
yup, and if people are looking for usage I just found a gist that shows how gob handling can be useful (writing to cache that allows the reading back to be castable into the correct structs) https://gist.github.com/pioz/ca5b7a11200f54afbd76dee7acbcc06...
Just because you already knew it all doesn't mean everyone else did. I hadn't seen it before.
Sometimes even when something was posted a few years ago some people just haven't seen it yet.
It's an entirely reasonable question to ask "is there any specific as to why this is being posted today?". If the answer is no, that's fine, but there may be extra context that is interesting and not obvious.
Ten thousand people, to be exact https://xkcd.com/1053/