From: Larry McVoy <lm@mcvoy.com>
To: Adam Thornton <athornton@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: [COFF] Re: On Bloat and the Idea of Small Specialized Tools
Date: Sun, 12 May 2024 12:47:07 -0700 [thread overview]
Message-ID: <20240512194707.GL9216@mcvoy.com> (raw)
In-Reply-To: <CAP2nic1zeJG7tkDbUnEMjxUG_TmYLwCQJhfS6Yt+E1w5s2s4cw@mail.gmail.com>
On Sun, May 12, 2024 at 12:34:20PM -0700, Adam Thornton wrote:
> But it does come down to the same argument as
> https://www.microsoft.com/en-us/research/uploads/prod/2019/04/fork-hotos19.pdf
>
> And it is true that while fork() is a great model for single-threaded
> pipeline-looking tasks, it's not really what you want for an interactive
> multithreaded application on your phone's GUI.
Perhaps a meaningless aside, but I agree on fork(). In the last major
project I did, which was cross platform {windows,macos, all the major
Unices, Linux}, we adopted spawn() rather than fork/exec. There is no way
(that I know of) to fake fork() on Windows but it's easy to fake spawn().
--lm
next prev parent reply other threads:[~2024-05-12 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 16:36 [TUHS] " Clem Cole
[not found] ` <CAGg_6+Ov6hYTxQ5M-hEBoOiUQ0UVRP0V+aVi0STKAALLDUGY7g@mail.gmail.com>
[not found] ` <CAEoi9W7FbGZFhiddHWWqdivGFfgFAj9nsUApomswfP56rqTMpQ@mail.gmail.com>
[not found] ` <20240511213532.GB8330@mit.edu>
2024-05-12 19:34 ` [TUHS] Re: [COFF] " Adam Thornton
2024-05-12 19:47 ` Larry McVoy [this message]
2024-05-12 20:13 ` [TUHS] Re: forking, " John Levine
2024-05-12 22:56 ` Dan Cross
2024-05-12 23:34 ` Larry McVoy
2024-05-13 1:34 ` Dave Horsfall
2024-05-13 13:21 ` Larry McVoy
2024-05-13 3:29 ` Andrew Warkentin
2024-05-12 20:43 ` [TUHS] " Dave Horsfall
2024-05-13 2:33 ` Alexis
2024-05-13 2:57 ` Warner Losh
2024-05-13 5:23 ` markus schnalke
2024-05-13 6:18 ` Andrew Warkentin
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=20240512194707.GL9216@mcvoy.com \
--to=lm@mcvoy.com \
--cc=athornton@gmail.com \
--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).