News for hackers. Stuff that matters.
Re:Gobs of data (2011) by buro9 on Monday December 04, 2023 @07:49AM (#38516613)
this is quite old, so I'm curious about what triggered it being posted again, has something happened / changed?
Re:Gobs of data (2011) by jstanley on Monday December 04, 2023 @07:56AM (#38516664)
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.

Re:Gobs of data (2011) by blowski on Monday December 04, 2023 @08:34AM (#38516988)
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.
Re:Gobs of data (2011) by sudhirj on Monday December 04, 2023 @08:02AM (#38516719)
Ten thousand people, to be exact https://xkcd.com/1053/
Re:Gobs of data (2011) by ash on Monday December 04, 2023 @09:25AM (#38517614)
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

Re:Gobs of data (2011) by buro9 on Monday December 04, 2023 @09:35AM (#38517746)
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...