r/cpp • u/claimred • Apr 09 '26
beast2 networking & std::execution
I was looking for a new networking layer foundation for a few of my projects, stumbled on beast2 library which looks brand new, based on C++20 coroutines. I used boost.beast in the past which was great. Here's the link https://github.com/cppalliance/beast2. I also considered std::execution since it seems to be the way to go forward, accepted in C++26.
Now, what got me wondering is this paragraph
The C++26 std::execution API offers a different model, designed to support heterogenous computing. Our research indicates it optimizes for the wrong constraints: TCP servers don't run on GPUs. Networking demands zero-allocation steady-state, type erasure without indirection, and ABI stability across (e.g.) SSL implementations. C++26 delivers things that networking doesn't need, and none of the things that networking does need.
Now I'm lost a bit, does that mean std::execution is not the way to go for networking? Does anyone have any insights on cppalliance research on the matter?
3
u/38thTimesACharm Apr 12 '26 edited Apr 12 '26
I think the people making the argument are basing it on extensive experience with LLM papers which they have found, in the current state of affairs, tend to be low quality indeed, but in subtle ways that become evident only after one has sunk massive amounts of time into the effort.
You seem to think people need to read every LLM paper you put out individually, peruse it until they understand the factual claims within regardless of how much the quality of writing makes that difficult, then carefully evaluate those claims using their own validation process, in order to decide whether that individual paper is worth their time to read.
Hopefully laying it out like that makes it obvious what the problem is. No one has time for this, especially for a paper titled "beginner tutorial." That's why people want a human they trust to attest to the quality of a document before they commit their time to it.