From: Luca Bruno <lethalman88@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>,
Eelco Dolstra <eelco.dolstra@logicblox.com>,
nix-dev <nix-dev@lists.science.uu.nl>
Subject: Re: Avoiding threads in the daemon
Date: Fri, 19 Dec 2014 22:36:41 +0100 [thread overview]
Message-ID: <CAHXTfc_tOa+4PKG186kx0s37EwT_mEyRwjq=XT-1Kd_iFcW+ow@mail.gmail.com> (raw)
In-Reply-To: <87ioh7tjg7.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 510 bytes --]
On Fri, Dec 19, 2014 at 10:31 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hmm, I’m not convinced about the whole threads-for-convenience approach
> à la Java. (I think the ideal is a single-threaded event loop; of
> course we want to avoid IoC, and this is where FRP or monads come in.)
>
It is instead for this case. It's not that you have to handle thousands of
connections. Threads simplify a lot compared to an event loop in C/C++.
Don't be fooled by the trends, it doesn't apply here.
[-- Attachment #1.2: Type: text/html, Size: 928 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
next prev parent reply other threads:[~2014-12-19 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 16:32 Avoiding threads in the daemon Ludovic Courtès
2014-12-19 18:20 ` Eelco Dolstra
2014-12-19 18:41 ` Shea Levy
2014-12-19 18:46 ` Eelco Dolstra
2014-12-19 21:31 ` Ludovic Courtès
2014-12-19 21:36 ` Luca Bruno [this message]
2014-12-20 0:11 ` Alexander Kjeldaas
2014-12-23 16:26 ` Eelco Dolstra
2014-12-26 22:02 ` Ludovic Courtès
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='CAHXTfc_tOa+4PKG186kx0s37EwT_mEyRwjq=XT-1Kd_iFcW+ow@mail.gmail.com' \
--to=lethalman88@gmail.com \
--cc=eelco.dolstra@logicblox.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=nix-dev@lists.science.uu.nl \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.