Re: Capy Review

Rainer Deyke wrote:
> I am not reviewing Capy/Corosio as replacements for ASIO, but as libraries in
> their own right.  Saying that ASIO does it that way is not a rationale, and
> referencing ASIO is not an explanation.

That's of course entirely true in principle, but there are attenuating
circumstances in this particular case.

All of Asio's design decisions are informed by years of heavy practice; they
encode hard earned truths. Vinnie's rule "when in doubt, do as Asio does"
is a good one to follow. Very good one to follow, in fact.

It would of course have been much better if we could, instead of "this is
because Asio", say "this is because of X, Y, Z, things that practical use of
Asio has surfaced over the years." The problem is that we can't; Chris
Kohlhoff, who is the sole source of truth about these X Y Z observations,
has scaled down his participation in our discussions dramatically.

That's of course not the optimal way to design software, but it is what it is.


_______________________________________________
Boost mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.boost.org/mailman3/lists/boost.lists.boost.org/
Archived at: https://lists.boost.org/archives/list/[email protected]/message/RQCN5MF5DMRCPNWPCF7HOAJLVPGVY4M4/