From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Matias Jose Seco Baccanelli <matias_jose_seco@autoproduzioni.net>
Cc: guile-user@gnu.org
Subject: Re: Curiosity: Microkernel implemented in Guile ?
Date: Thu, 23 Jun 2022 09:02:56 +0200 [thread overview]
Message-ID: <87wnd7lu93.fsf@web.de> (raw)
In-Reply-To: <20220623081120.091b84b7.matias_jose_seco@autoproduzioni.net>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
Moin Matias,
Matias Jose Seco Baccanelli <matias_jose_seco@autoproduzioni.net> writes:
> Isn't a cool mix the functional approach of Guile and the modular one
> of Microkernel ? (and loads of more features i suppose!)
>
> Feels like a nice recipe for User Empowerment !
The most practical way forwards for that might be Guile bindings for the
Hurd. Those would enable to move more Guile in incrementally while
always keeping a working state.
The incubator already has bindings for common-lisp.¹ Those could be a
good starting point. And there is Guix for the Hurd.
http://git.savannah.gnu.org/cgit/hurd/incubator.git/?h=clisp
Those bindings would allow for stuff like this to be done in Guile:
Deferred Authorization translator for the Hurd
https://www.draketo.de/software/hurd-authorization-translator
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-23 7:02 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 [this message]
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
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=87wnd7lu93.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=matias_jose_seco@autoproduzioni.net \
/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).