That said, what makes for a compelling Go blog? I do see them around, yet I don’t subscribe to them. It’s difficult having topics that grab my interest. I can read about people building their own software all day, but I’m hardly interested in the actual code. Libraries are maybe a little more interesting, but only if they can be potentially useful to me. And no, I don’t care what performance multiplier your JSON parser has.

This is the disadvantage of writing about backend tech. You can easily enjoy the efforts of web frontend developers in a much more superficial way: go to their site, and start browsing. This is harder to do with Go bloggers. You have to check out their code, build it, and if it’s a library, use it. All activities that require one to be at a desktop, which is not where I tend to read such things.