4 ms·
You need to keep the UI responsive, so you hand off all resource or cpu heavy work off the UI thread, give back control to rendering and responding to user inpu
by oaiey 4y ago
You need to keep the UI responsive, so you hand off all resource or cpu heavy work off the UI thread, give back control to rendering and responding to user input ... and later need to collect the results in the UI thread to change the UI state.
It is about doing things in parallel. There are many ways on how to achieve that, I am just nit picking on performance.
- cube2222 4y agoThen I think we misunderstood each-other. Go is asynchronous-first, it just doesn't use the (flawed) async-await semantic to model asynchronicity.