3 ms·
All these intros to asynchronous programming fail to address the most interesting (and arguably most important yet also most difficult) case, which is asynchron
by clarry 7y ago
All these intros to asynchronous programming fail to address the most interesting (and arguably most important yet also most difficult) case, which is asynchronicity on a modern multi-core server. Instead, threads and event loops are presented as mutually exclusive strategies.. naively using one thread for every connection doesn't scale, and naively using event loops means you're stuck running it all on one core, which doesn't scale.
- RossBencina 7y agoI guess that's because they are "intros," and often multi-core event loops are implemented by the language runtime or some threadpool library. This is a good watch: Dmitry Vyukov — Go scheduler: Implementing language with lightweight concurrency (Oct 14, 2019) https://www.youtube.com/watch?v=-K11rY57K7k https://www.youtube.com/watch?v=-K11rY57K7k