From: "Ricardo G. Herdt" <r.herdt@posteo.de>
To: guile-user <guile-user@gnu.org>
Subject: Re: Curiosity: Microkernel implemented in Guile ?
Date: Thu, 23 Jun 2022 09:01:21 +0000 [thread overview]
Message-ID: <64ad713643b760dd1ee90a1a5bd5d76e@posteo.de> (raw)
In-Reply-To: <CAA2Xvw+Tq491b1kw5aTPOX_hq9-eKOOHsB63EH9riodziXrOaw@mail.gmail.com>
Never tried it myself, but in case you are interested in exploring
Scheme for this kind of development, check Loko Scheme, which runs on
bare-metal and is developed to be a "platform for application and
operating system development":
https://scheme.fail/
There is also a #loko channel on libera.
Ricardo
Am 23.06.2022 08:57 schrieb Mikael Djurfeldt:
> To my knowledge, the answer is no. No such attempt has been made.
>
> The Guile language is essentially Scheme. Scheme lacks various
> constraints,
> with regard to typing, memory management, etc, needed for it to be
> compiled
> to predictable and near maximally efficient machine code, something
> which
> is needed, at least for portions of the code, when implementing a
> useful
> microkernel.
>
> In theory, it is possible to extend the language for such purposes,
> though.
>
> An alternative high level language which can be used to implement a
> kernel
> is Rust.
>
> Best regards,
> Mikael
>
> Den tors 23 juni 2022 08:12Matias Jose Seco Baccanelli <
> matias_jose_seco@autoproduzioni.net> skrev:
>
>> Good morning Guilers!
>> Being a huge fan of Libre Software and Guile powers, i was having a
>> big
>> curiosity in regards to the kernel languages arena:
>> was ever made an attempt to implement a Microkernel from scratch in
>> Guile language ?
>> 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 !
>> Just asking as a total beginner on this topic,
>> Happy Hacking!
>> Matias
>>
>>
next prev parent reply other threads:[~2022-06-23 9:01 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 [this message]
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
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=64ad713643b760dd1ee90a1a5bd5d76e@posteo.de \
--to=r.herdt@posteo.de \
--cc=guile-user@gnu.org \
/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).