ASIO is too complicated for mere mortals with too many gotchas. I dont need a ten ways to do the same thing. I just need something that works correctly without trying too hard to understand and avoid all the trip-wires and land mines that seem to repeatedly cause potential users trouble. IMO, leave ASIO alone, and build new libraries that use it but hidden and most importantly cover 90% of the normal use cases correctly. On 8/20/25 5:40 AM, Claudio DeSouza via Boost wrote:
Just to be clear, “the above reasons” are that you suspect Chris is copying other people’s homework. I think you need to show specific examples, because I don’t think I’ve seen any example where this would be a fair characterization.
I'm also a bit confused about this, because there seems to be conflicting statements even in this thread. Vinnicius early, whilst praising Chris policy, said:
"Every time I've reached out to improve FreeBSD support (even in niche cases), the changes were accepted (most of the times Chris rewrote the changes himself, but got the job done anyways)."
And
"You have to follow the commit history to see if your changes got accepted because most of the time Chris rewrites the patches to not delay fixes even further (instead of asking for changes and then waiting until you get the patches to his liking)."
So I'm not sure how to interpret that, and other Asio contributors could better explain what normally happens in these cases. _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/3X4L35UE...