> in fat client apps it's all about event handling and data flow, co-rotines are not very useful there. I would suggest that coroutines can solve event handlin

> in fat client apps it's all about event handling and data flow, co-rotines are not very useful there. I would suggest that coroutines can solve event handling problems quite nicely. This is not exactly a novel idea either. There are toolkits in the wild that are designed to work exactly like that. From what I understand, there hasn't been any serious exploration of building UIs in Go, but I think its native coroutine/channel support has the potential to provide some interesting ways to handle events that are generally shied away from in languages where coroutines are not as easily used.