@grips Yeah, I recognized that. I like the whole interfaces and how easy it is to share memory between separate go routines.
It gets a bit iffy once you start working with channels, avoiding deadlocks is the hardest part. But once you are beyond that every thing else is just implementation details.
@grips With any programming language you need a project to get to the bottom of what makes a language tick. The problem with parallel processes (and the contexts and channels that come along with it) is that no small project will require this =)
@grips I've still been meaning to write a fediverse server in Go. But that idea is on the backburner due to time. :-)