public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Connell (Gmail)" <matthewdconnell@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rusty problems
Date: Tue, 27 Apr 2021 16:17:20 -0500	[thread overview]
Message-ID: <f360b862df20f7eb7d9a54e6442c0f1d1503239e.camel@gmail.com> (raw)
In-Reply-To: <YIh5tzP8L7WmVG98@ACM>

On Tue, 2021-04-27 at 20:53 +0000, Alan Mackenzie wrote:
> I know I could plump for the -bin package.  Maybe I should.

I did, recently. 

Anecdotes/opinions/rant follows.  Feel free to ignore, I just wanted to
vent because the issue is fresh in my mind.

...

Some things just aren't worth building from source.  Rust is so heavy,
convoluted, ill-supported and slow that I just can't be bothered to
spend hours of compile time on getting a slightly-less-awful version of
it for my system(s).  And given how a desktop environment now requires
a Javascript engine to parse configurations (that's a separate
complaint), and spidermonkey requires rust to build, there's no
avoiding it for my needs, so I just cut bait.

The same can be said for GHC (the Glasgow Haskell Compiler).  I can't
do my day-to-day without shellcheck, but spending 8 hours to build a
compiler for shellcheck (and sometimes pandoc) frankly sucks.  This
isn't gentoo's fault, or anyone's fault really.  Languages are complex
and the code to bootstrap compile them isn't easy.  Its above my skill
level, that's for sure.

8+ years of gentoo has taught me many lessons, chief among them is to
pick my battles.  If there is some must-have or must-avoid USE flag, or
a killer feature that's missing from the bin build, then I'll swallow
the pill and take the time to compile it.  If not, I've got better
things to do with my electricity.



  reply	other threads:[~2021-04-27 21:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 20:53 [gentoo-user] Rusty problems Alan Mackenzie
2021-04-27 21:17 ` Matt Connell (Gmail) [this message]
2021-04-27 22:00   ` Michael
2021-04-28  8:58     ` Wols Lists
2021-04-28  9:21       ` Michael
2021-04-27 22:02 ` tastytea
2021-04-27 22:38 ` Teru Yuu
2021-04-27 23:09 ` Neil Bothwick
2021-04-28 11:12   ` Alan Mackenzie
2021-04-28 12:03     ` Neil Bothwick
2021-04-28 22:05       ` antlists
2021-04-28 22:54         ` Neil Bothwick
2021-04-28  7:04 ` J. Roeleveld
2021-04-28  7:25   ` Andrew Lowe
2021-04-29  6:36 ` Adam Carter

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=f360b862df20f7eb7d9a54e6442c0f1d1503239e.camel@gmail.com \
    --to=matthewdconnell@gmail.com \
    --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