From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Wayne <waynedpj@ingiro.xyz>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Shepherd and Guille
Date: Thu, 08 Nov 2018 08:58:49 +0100 [thread overview]
Message-ID: <87a7mkm24m.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20181107231234.Horde.GJcOfWxRUgR6leHv2K2Odev@mail.ingiro.xyz>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
> the point about using GC/JIT/etc. languages for "critical" software like init
> seemed somewhat worth investigating.
Actually, why? I read this, and to me it sounded like the following reasoning:
"if it's critical, then it has to be a _systems_ language, i.e. C or C++ (or
rust?)".
The author seems to contradict himself and be very confused about this. If
you read the Shepherd paragraph, compare:
> The decision to write important system-level software in non-memory-safe languages such as C and
> C++ has been criticised.
vs.
> my concern is that it’s written in Guile, an interpreted (or
> bytecode-interpreted) language with garbage collection – and
Why is it a concern now that the author just said doing the other way around is
criticized? Argumentation is completely lacking.
> I see both the “interpreted” and “garbage collection” parts as undesirable for system-level software
> (especially for a potential init).
Why? How are the two related? The author might be confabulating between kernel
and system-level.
> Interpreted software will be less efficient (if not in actual speed, since
> I’ll acknowledge that JITs can do amazing things, at least in memory usage)
So if not actual speed, then what is less efficient? The author does not say...
Actually the more I read it, the more it sounds like a complete heap of
non-sense :D
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-08 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 0:39 Shepherd and Guille Wayne
2018-11-01 4:19 ` Vladimir Sedach
[not found] ` <87o9b9ig4l.fsf@exinda.orion.oneofus.la>
2018-11-04 9:39 ` Pierre Neidhardt
2018-11-08 4:12 ` Wayne
2018-11-08 7:58 ` Pierre Neidhardt [this message]
2018-11-09 5:18 ` Vladimir Sedach
[not found] ` <5be518c9.1c69fb81.90d67.495dSMTPIN_ADDED_BROKEN@mx.google.com>
2018-11-10 1:46 ` Maxim Cournoyer
2018-11-13 4:22 ` Wayne
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=87a7mkm24m.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=waynedpj@ingiro.xyz \
/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.