John Cowan wrote:
> As someone who generally favors bits over API, I think the posterchild
> for the API approach is the sockets API. I can scarcely imagine anyone
> who would avoid this in favor of manipulating TCP, UDP, and IP bits
> themselves. If there's no implementation of sockets (even a semi-broken
> one like Winsock), network programming is a plain non-starter on that
> platform until it's ported.
Yep. And what's surprising is that as far as I can remember, the
sockets API today is more or less what first shipped with 4.2bsd in
1983... it's surprising that they got it more or less right the first
time.
I wonder if they'll still be using SAX in 2020... -Tim