From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Matias Jose Seco Baccanelli <matias_jose_seco@autoproduzioni.net>,
Guile User <guile-user@gnu.org>
Subject: Re: Curiosity: Microkernel implemented in Guile ?
Date: Fri, 24 Jun 2022 07:45:32 +0200 [thread overview]
Message-ID: <87k096k3km.fsf@web.de> (raw)
In-Reply-To: <CAPjoZodap5YPO2to7gNo=e2jVKyHAqQkr6x0VULE5JutLXpf1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Nala Ginrut <nalaginrut@gmail.com> writes:
> Agreed, Guile's design was widened. But I think we are talking about
> different "low-level", for Hurd, Guile can be used to write OS
> components, say, filesystem. However, except for GNU Mach, most OS
> components are implemented in userland, and Guile is good for that,
> this is what it's designed for. The "low-level" in my mind is to write
> GNU Mach part, which is not suitable for Guile.
Ah, there’s you’re right.
Though the loko linked by Ricardo sounds interesting. The license is
AGPL compatible.
And the tagline is neat: “Give it some RAM and a supported machine, and
it gives you a REPL.”
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2022-06-24 5:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 6:11 Curiosity: Microkernel implemented in Guile ? Matias Jose Seco Baccanelli
2022-06-23 6:57 ` Mikael Djurfeldt
2022-06-23 9:01 ` Ricardo G. Herdt
2022-06-24 5:40 ` Dr. Arne Babenhauserheide
2022-06-23 7:02 ` Dr. Arne Babenhauserheide
2022-06-23 7:32 ` zimoun
2022-06-23 7:34 ` Maxime Devos
2022-07-02 9:47 ` Matias Jose Seco Baccanelli
2022-07-04 2:49 ` Blake Shaw
2022-06-23 9:13 ` pukkamustard
2022-06-23 10:09 ` Nala Ginrut
2022-06-23 11:22 ` Maxime Devos
2022-06-23 15:38 ` Nala Ginrut
2022-06-23 22:03 ` Dr. Arne Babenhauserheide
2022-06-24 1:12 ` Nala Ginrut
2022-06-24 5:45 ` Dr. Arne Babenhauserheide [this message]
2022-06-24 7:01 ` Jean Abou Samra
2022-06-24 7:41 ` Dr. Arne Babenhauserheide
2022-06-25 14:35 ` Jean Abou Samra
2022-06-26 6:22 ` Dr. Arne Babenhauserheide
2022-06-26 7:55 ` Ricardo Wurmus
2022-06-26 8:32 ` Dr. Arne Babenhauserheide
2022-06-28 22:23 ` Jean Abou Samra
2022-06-26 10:37 ` Nala Ginrut
2022-06-28 22:30 ` Jean Abou Samra
2022-06-24 12:42 ` Nala Ginrut
2022-06-24 3:27 ` Ognen Duzlevski
2022-06-24 21:24 ` Dr. Arne Babenhauserheide
2022-06-23 12:13 ` Ognen Duzlevski
2022-06-23 13:30 ` Dr. Arne Babenhauserheide
2022-06-23 17:47 ` Paul Emsley
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k096k3km.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=matias_jose_seco@autoproduzioni.net \
--cc=nalaginrut@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).