public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Remove rust completely
Date: Thu, 12 May 2022 17:21:57 +0100	[thread overview]
Message-ID: <7e38e311-1b45-3baf-dc0f-1b4256f4a72d@youngman.org.uk> (raw)
In-Reply-To: <CAFvvX=Y+zQYegVbAne=je85vGNX0a3QQ-P5tpuZTw=Lie1bkWA@mail.gmail.com>

On 12/05/2022 02:41, Mansour Al Akeel wrote:
> And yes, the compile time is one of the factors in not wanting it on
> my system. The second factor is a natural reaction toward feeling that
> I am forced to have it.
> Another reason is the growing collection of compilers and development
> tools and their build time (gcc, bin-utils, llvm, clang ... etc.) and
> now rust.

Tongue in cheek, but have you tried doing away with gcc, clang etc?

If you're going to use a source-based system, a bunch of compilers 
"comes with the territory".

Many people see Rust as a "better C than C", so that's why it's becoming 
popular. (Oh, and does Rust have its own compiler, or is Rust just part 
of llvm?).

The way things are going you might find all you need is the llvm 
collection, and gcc will be obsolete ...

Cheers,
Wol


  parent reply	other threads:[~2022-05-12 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  0:22 [gentoo-user] Remove rust completely Mansour Al Akeel
2022-05-12  0:25 ` Julien Roy
2022-05-12  0:55   ` Miles Malone
2022-05-12  1:41     ` Mansour Al Akeel
2022-05-12  2:02       ` cal
2022-05-12  2:24         ` Mansour Al Akeel
2022-05-12  3:19           ` Matt Connell
2022-05-12  2:05       ` [gentoo-user] " Grant Edwards
2022-05-12 16:21       ` Wols Lists [this message]
2022-05-12  2:01   ` [gentoo-user] " Mansour Al Akeel
2022-05-14 11:04 ` Michael Orlitzky

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=7e38e311-1b45-3baf-dc0f-1b4256f4a72d@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@lists.gentoo.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