From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: "bingmatv@outlook.com" <bingmatv@outlook.com>
Cc: rms@gnu.org, libc-help@sourceware.org, help-bash@gnu.org
Subject: Re: Richard M. Stallman says GNU/Linux, but Rust lang ecosystem is growing.
Date: Sun, 31 Mar 2024 11:04:01 -0300 [thread overview]
Message-ID: <D7ABDF35-7380-4874-8D6C-9A285080D2A1@linaro.org> (raw)
In-Reply-To: <MW3PR22MB2284001434D57BF5E58A10B0D0382@MW3PR22MB2284.namprd22.prod.outlook.com>
> On 31 Mar 2024, at 09:44, bingmatv--- via Libc-help <libc-help@sourceware.org> wrote:
>
> Richard Matthew Stallman tell people to say GNU/Linux to spread free software, but Rust programming language ecosystem is growing fastly, Rust focuses on memory safety. If one day, Rusty alternative of GNU software is published, but they're not developed by GNU project, someone may say "rust-lang/Linux" instead of "GNU/Linux", which is very bad for spreading free software. So I suggest GNU project use Rust to rewrite all GNU software to prevent future people from saying "rust-lang/Linux" instead of "GNU/Linux", because Rust language users may only support memory safety, but not free software movement. In conclusion: At least glibc and bash need to be rewritten in Rust, glibc is the interface of user-space programs and kernel syscall, I think it's better to write librust instead of glibc, preventing future people from saying "rust-lang/Linux" that may not support free software movement, since rust-lang/Linux doesn't mention GNU and only supports memory safety. And finally, Rust focuses on memory safety, it's currently safer than C++.
Was it generated using a LLM? In any case you do have some libc implemented in rust (the one from redox project for instance), so you might check this out and send patches to implement the missing parts.
next prev parent reply other threads:[~2024-03-31 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 12:43 bingmatv
2024-03-31 14:04 ` Adhemerval Zanella [this message]
2024-03-31 14:50 ` tomas
2024-04-02 1:44 ` Dennis Clarke
2024-04-07 7:27 ` 馬 冰
2024-04-07 7:45 ` Konstantin Kharlamov
2024-04-11 12:05 ` 馬 冰
2024-04-11 12:12 ` Konstantin Kharlamov
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=D7ABDF35-7380-4874-8D6C-9A285080D2A1@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=bingmatv@outlook.com \
--cc=help-bash@gnu.org \
--cc=libc-help@sourceware.org \
--cc=rms@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).