From: Maxime Devos <maximedevos@telenet.be>
To: Matias Jose Seco Baccanelli <matias_jose_seco@autoproduzioni.net>,
guile-user@gnu.org
Subject: Re: Curiosity: Microkernel implemented in Guile ?
Date: Thu, 23 Jun 2022 09:34:25 +0200 [thread overview]
Message-ID: <1614daa41ab3566163045f571a4ca007cd8bc417.camel@telenet.be> (raw)
In-Reply-To: <20220623081120.091b84b7.matias_jose_seco@autoproduzioni.net>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
Matias Jose Seco Baccanelli schreef op do 23-06-2022 om 08:11 [+0200]:
> Feels like a nice recipe for User Empowerment !
How does this empower users? Sure, if the user is a programmer they
can modify their custom microkernel in Scheme, but then you have a very
niche OS that practically no other software already supports, which is
very inconvenient for the user and the user will have practical
difficulties sharing the software with other people using other OSes,
so I think you're better of modifying another pre-existing microkernel
to be usable from Guile (see answer by Dr. Arne Babenhauserheide).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-23 7:34 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 [this message]
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=1614daa41ab3566163045f571a4ca007cd8bc417.camel@telenet.be \
--to=maximedevos@telenet.be \
--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).