Get the latest tech news

The 4-chan Go programmer

A very silly concurrency exercise in using Go channels that send channels that send channels that send channels.

And these novices didn't realize what a silly thing this is to do, thinking instead that getting a working program that used this many layers of pointer indirection was actually a sign of expertise. If you enable logging by uncommenting the first line, you'll get output like this that lets you see the branching factor at each layer of channel production / consumption: There are a lot of reasons not to do this in real code: the difficulty of implementation and debugging, having a little self-respect, not wanting to be clubbed to death by your peers' bulky mechanical keyboards, etc.

Get the Android app