gringo

Agreed on both counts, actually. 1. GoDoc is actually great as a reference (i.e.: as Go's answer to Python's docstrings). I suppose I'm instead yearning for someone to hold my hand with regards to how I'm supposed to compose module primitives together, but that's admittedly a tutorial, not a docstring. So that said, I do like the Python community's insistance on comprehensive docs/tutorials, and I think the Go community needs more of that. 2. Very fast if you come from python, and fast enough if you're doing IO-bound stuff ... still slow if you're trying to do CPU-bound stuff. WRT point #2, I like Gringo a lot: https://github.com/textnode/gringo

I've been looking into false sharing and other pitfalls of parallelism on multi-core systems. http://en.wikipedia.org/wiki/False_sharing It seems like our multi-core hardware isn't that well thought out yet. In particular, locks can cause false sharing. Even go channels are based on locks! I would love to see some kind of annotation in golang for padding certain structs to cache-line boundaries. This value can be read from most processors, so it could be done in a cross-platform fashion. The gringo ring-channel library has to do its own padding to avoid false sharing. https://github.com/textnode/gringo/blob/master/gringo.go type Gringo struct { padding1 [8]uint64 lastCommittedIndex uint64 padding2 [8]uint64 nextFreeIndex uint64 padding3 [8]uint64 readerIndex uint64 padding4 [8]ui