3 ms·
I hear you, I'd love to have the same thing. Still the big deal about co-routines for me is not mainly raw performance (or core-utilization) but rather the pro
by moe 18y ago
I hear you, I'd love to have the same thing.
Still the big deal about co-routines for me is not mainly raw performance (or core-utilization) but rather the programming model. I've literally slashed the LOC-count in half for some of our projects just by moving to co-routines, that's what I call a productivity boost.
Also I find myself enjoying co-routines much more than the tangled mess of callbacks and data-locality issues in the multithreaded world.
- MaysonL 18y agoI still remember with fondness the first coroutines I wrote, almost 35 years ago: it seemed like a really cool hack to connect a producer of bytes to a consumer of them (both already written, just 6 lines of assembler plus a little bit of init code).