From: Rob Pike <robpike@gmail.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] non-blocking IO - threads
Date: Wed, 3 Jun 2020 09:09:08 +1000 [thread overview]
Message-ID: <CAKzdPgxH=Ub-EZLmNnRR4W75ipqjt6a_UmwG5nPqwUDRopxOGw@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgxQnFWf-E99zEyZJBB5z23ZUKwj-Dffe9y5if9R-w3Qpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
To be more forthcoming, there was a long period when the received wisdom
was that threads were unmanageable. But that was a category error: The
programming model in POSIX and others was what made it hard. The
fundamental concepts are a tiny step harder than trivial, and it was not
hard to build a programming model that matched them.
The first mistake people made was to split "thread" from "process". What
those words mean today is not what they meant a generation ago.
For me, it's like the mess sockets made of networking. Our programming
models could be so much simpler than what we are required to deal with.
-rob
[-- Attachment #2: Type: text/html, Size: 779 bytes --]
next prev parent reply other threads:[~2020-06-02 23:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 14:19 [TUHS] non-blocking IO Paul Ruizendaal
2020-06-02 17:45 ` Paul Winalski
2020-06-02 17:59 ` arnold
2020-06-02 18:53 ` Paul Winalski
2020-06-02 19:18 ` Clem Cole
2020-06-02 21:15 ` Lawrence Stewart
2020-06-02 22:03 ` [TUHS] non-blocking IO - threads Jon Steinhart
2020-06-02 23:05 ` Rob Pike
2020-06-02 23:09 ` Rob Pike [this message]
2020-06-02 23:21 ` Larry McVoy
2020-06-03 0:39 ` Rob Pike
2020-06-02 23:12 ` Jon Steinhart
2020-06-03 16:42 ` Paul Winalski
2020-06-03 17:57 ` Jon Forrest
2020-06-03 5:38 ` [TUHS] Unix on the Arpanet Lars Brinkhoff
2020-06-03 12:23 ` Lawrence Stewart
2020-06-02 18:23 ` [TUHS] non-blocking IO Dan Cross
2020-06-02 18:56 ` Paul Winalski
2020-06-02 19:23 ` Clem Cole
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='CAKzdPgxH=Ub-EZLmNnRR4W75ipqjt6a_UmwG5nPqwUDRopxOGw@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=jon@fourwinds.com \
--cc=tuhs@minnie.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).