From: John Floren <john@jfloren.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Research Datakit notes
Date: Tue, 28 Jun 2022 18:28:54 +0000 [thread overview]
Message-ID: <e07eaaf5-71f0-e520-232f-bc2256e18dfa@jfloren.net> (raw)
In-Reply-To: <CAKzdPgwwf9aMOi4_PceSuuDBJEH7r+znqMxWX7nbeiBtn3KaDg@mail.gmail.com>
On 6/28/22 05:45, Rob Pike wrote:
> [...] I know it's amazing engineering and
> all that, but why aren't we allowed to program the I/O without all that
> fuss? What makes networks so _different_? A telling detail is that the
> original sockets interface had send and recv, not read and write. From
> day 1 in Unix land at least, networking was special, and it remains so,
> but I fail to see why it needs to be.
>
> It just seems there has to be a better way. Sockets are just so
> unpleasant, and the endless nonsense around network configuration doubly so.
>
I was pretty sad when netchans were discontinued. A colleague was
sufficiently attached to them that he kept his own branch of the library
going for a while.
john
next prev parent reply other threads:[~2022-06-28 18:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 23:01 [TUHS] " Paul Ruizendaal
2022-06-25 23:09 ` [TUHS] " Larry McVoy
2022-06-25 23:57 ` Rob Pike
2022-06-26 1:17 ` Paul Ruizendaal
2022-07-02 2:51 ` Grant Taylor via TUHS
2022-07-02 2:57 ` Larry McVoy
2022-06-28 10:38 ` Derek Fawcus
2022-06-28 12:36 ` Rob Pike
2022-06-28 12:45 ` Rob Pike
2022-06-28 13:33 ` Dan Cross
2022-06-28 21:19 ` Lawrence Stewart
2022-06-28 21:34 ` Richard Salz
2022-06-29 6:07 ` Stuart Remphrey
2022-06-28 16:11 ` Tom Teixeira
2022-06-28 18:28 ` John Floren [this message]
2022-06-28 12:47 ` Rich Morin
2022-06-28 13:13 ` Marc Donner
2022-06-28 14:41 ` Clem Cole
2022-06-28 15:54 ` Tom Teixeira
2022-06-28 17:05 ` Adam Thornton
2022-06-28 17:43 ` John Labovitz
2022-06-28 22:45 ` [TUHS] HTTP (was Re: Re: Research Datakit notes) Derek Fawcus
2022-06-26 1:41 ` [TUHS] Re: Research Datakit notes Anthony Martin
2022-06-26 9:52 ` Ralph Corderoy
2022-06-26 11:04 ` Paul Ruizendaal
2022-06-29 20:21 ` Paul Ruizendaal
2022-06-26 2:19 Noel Chiappa
2022-06-26 9:46 ` steve jenkin
2022-06-26 20:35 ` Erik Fair
2022-06-26 21:53 ` Steve Jenkin
2022-06-26 10:16 ` Paul Ruizendaal via TUHS
2022-06-26 13:07 ` John Cowan
2022-06-26 13:35 ` Larry McVoy
2022-06-26 13:58 ` John Cowan
2022-06-27 0:43 Noel Chiappa
2022-06-27 3:00 ` Erik Fair
2022-06-27 21:40 Noel Chiappa
2022-06-27 22:40 ` George Michaelson
2022-06-28 15:50 Noel Chiappa
2022-06-28 21:32 ` Lawrence Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e07eaaf5-71f0-e520-232f-bc2256e18dfa@jfloren.net \
--to=john@jfloren.net \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).