3 ms·
Yeah, and that's why Go code is a spaghetti of communicating via channels, rather than callbacks.
by heavenlyblue 8y ago
Yeah, and that's why Go code is a spaghetti of communicating via channels, rather than callbacks.
- emersion 8y agoEach code in each goroutine is synchronous. That's what makes it simpler than callbacks.
- weberc2 8y agoCallbacks are prolific in Go; not sure where you're getting this from...
- johnydepp 8y agoGo channels are very handy and magnitude of less spaghetti than futures. And goroutines have good performance. I think people are used to futures etc, that's why the new concept feels strange. I think the goroutines and channels are the biggest features which compensates for generics.