Great breakdown of design tradeoffs in modern C++! The Asio vs std::ranges comparison really drives home how 20+ years ofproduction use trumps theoretical elegance. I've defintely run into this when working with network buffers - ended up with a mess of overloads before realizing the issue was thinking in types instead of operations. The virtual boundary insight is lowkey brilliant, that's exactly where concrete types make sense while keeping the API layer compositional.
Thanks. Can you believe the entire paper was AI-generated? Anyway... I've been building the successor to Boost.Asio (https://github.com/cppalliance/corosio) and I struggled for a while because on the one hand I like the compositional power of concepts but on the other hand I have grown to dislike header-only libraries which are template-only. I think I found the right balance now :)
Nice and clear! Thanks!
Great breakdown of design tradeoffs in modern C++! The Asio vs std::ranges comparison really drives home how 20+ years ofproduction use trumps theoretical elegance. I've defintely run into this when working with network buffers - ended up with a mess of overloads before realizing the issue was thinking in types instead of operations. The virtual boundary insight is lowkey brilliant, that's exactly where concrete types make sense while keeping the API layer compositional.
Thanks. Can you believe the entire paper was AI-generated? Anyway... I've been building the successor to Boost.Asio (https://github.com/cppalliance/corosio) and I struggled for a while because on the one hand I like the compositional power of concepts but on the other hand I have grown to dislike header-only libraries which are template-only. I think I found the right balance now :)