From: Richard <richard_siegfried@systemli.org>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Wouldn't Zig be more suitable than rust? In the Linux kernel
Date: Fri, 27 Sep 2024 13:56:20 +0200 [thread overview]
Message-ID: <be3f5952-b5d3-43e5-9610-cfbc97c1c9e3@systemli.org> (raw)
In-Reply-To: <CAPegGh-FyJvBUMghuwAP9HSXfmxBL+N_77ubCysYmi==EqDD6Q@mail.gmail.com>
>
> What do you think?
>
I'd like to add that sociological and organisational matters are often
(and I think here too) more important than technical reasons. If one of
the languages has a bigger community (and more importantly more people
with the motivation to make it work for linux) that's what will make the
difference. From what it looks like to me currently Rust has the better
marketing and the bigger community.
It could also make a big difference if a company came up that champions
one of the languages and wants to write kernel modules with it
-- Richard
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-09-27 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 21:07 Wouldn't Zig be more suitable than rust? In the Linux kernel Manuel Quintero Fonseca
2024-09-24 0:11 ` Joshua Rose
2024-09-24 0:58 ` Jeffrey Walton
2024-09-27 11:56 ` Richard [this message]
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=be3f5952-b5d3-43e5-9610-cfbc97c1c9e3@systemli.org \
--to=richard_siegfried@systemli.org \
--cc=kernelnewbies@kernelnewbies.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 NNTP newsgroup(s).