News for hackers. Stuff that matters.

A comment on Distributed Systems Programming Has Stalled. Parent comment

Re:Distributed Systems Programming Has Stalled by hinkley on Thursday February 27, 2025 @01:11PM (#43196850)
Coroutines basically make the same observation as transmit windows in TCP/IP: you don’t send data as fast as you can if the other end can’t process it, but also if you send one at a time then you’re going to be twiddling your fingers an awful lot. So you send ten, or twenty, and you wait for signs of progress before you send more.

On coroutines it’s not the network but the L1 cache. You’re better off running a function a dozen times and then running another than running each in turn.

[ Parent | on HN ]
Re:Distributed Systems Programming Has Stalled by gmadsen on Thursday February 27, 2025 @06:04PM (#43199563)
fair enough, that was the design choice c++ went with to not break ABI and have moveable coroutine handles

rust accepted the tradeoff and can do pure stack async,

there are things you can do in c++ to not get the dynamic allocation to heap, but it requires a custom allocator + predefining size of coroutines.

https://pigweed.dev/docs/blog/05-coroutines.html

[ Parent | on HN ]