4 ms·
It's not like C++ devs have much choice but to deal with this stuff since Asio was effectively kicked out of standardisation. Asio also has its flaws, but the
by secondcoming 3y ago
It's not like C++ devs have much choice but to deal with this stuff since Asio was effectively kicked out of standardisation.
Asio also has its flaws, but the async story in C++ has quite the cognitive overload.
- gumby 3y ago> since Asio was effectively kicked out of standardisation I saw that that happened but didn't have time to dig into it. Asio has been in use for a couple of decades so was surprised it didn't pass muster. Could anyone summarize what went wrong? Admittedly what Nebler is talking about does look a lot simpler, but is it a reasonably full replacement for the functionality of Asio?
- gpderetta 3y agoIt is still not clear to me what happened. One issue is that there was no big company behind asio and some companies were looking for a more general framework. Still for what I have seen, sender/receiver only deal with composing async operations, the proposal so far still lack an actual network executor, so it is far from being ready. This is a shame I think, because while asio might not have been perfect it means that in 2024 C++ still lacks a network library.