From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: the importance of rust-build-system [Fwd: [tor-dev] Tor in a safer language: Network team update from Amsterdam]
Date: Sun, 02 Apr 2017 00:22:14 +0200 [thread overview]
Message-ID: <87r31bg44p.fsf@gnu.org> (raw)
In-Reply-To: <20170401185824.GA27445@jasmine> (Leo Famulari's message of "Sat, 1 Apr 2017 14:58:24 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Apr 01, 2017 at 07:58:41AM +0000, ng0 wrote:
>> tor is seriously considering to switch to rust. I have my own open
>> bugs / roadmap points which depend on our rust-build-system working.
>> tor will not switch immediately, but it shows the importance of having a
>> working rust-build-system. Firefox will switch at some point.
>
> It's immediately important because the latest version of librsvg (used
> to create the GuixSD GRUB background image) is written in Rust. We could
> even update that package "the hard way", without a full
> rust-build-system.
For librsvg and Tor, a switch to Rust is both good news and bad news:
it’s good news because using a memory-safe language is indeed a wise
decision, but it’s bad news because it introduces a single point of
trust (opaque Rust binaries built by Mozilla) in our dependency graph.
Ludo’.
next prev parent reply other threads:[~2017-04-01 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 7:58 the importance of rust-build-system [Fwd: [tor-dev] Tor in a safer language: Network team update from Amsterdam] ng0
2017-04-01 18:58 ` Leo Famulari
2017-04-01 22:22 ` Ludovic Courtès [this message]
2017-12-08 10:04 ` ng0
2017-04-02 13:02 ` ng0
2017-04-02 13:05 ` ng0
2017-04-02 22:35 ` Danny Milosavljevic
2017-12-07 20:59 ` ng0
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=87r31bg44p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.