From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile python update is wedged [Was: Fragile rust update is wedged].
Date: Fri, 2 May 2025 22:17:01 +0000 [thread overview]
Message-ID: <aBVEXQwfBwSGLw4-@MAC.fritz.box> (raw)
In-Reply-To: <c7817ad8-4d41-4365-9d2e-68c69fd2cc31@gentoo.org>
Hello, Jay.
On Fri, May 02, 2025 at 14:44:06 -0700, Jay Faulkner wrote:
> On 5/2/25 2:15 PM, Alan Mackenzie wrote:
> > If that's the way they see things, it would seem that having a project
> > dependent on rust should figure high on that project's risk list.
> This is ... a non-actionable take, regardless of if I agree with it or not.
OK.
> Do you expect Gentoo to replace Firefox? pycryptography? a heavily used
> SVG library? kernel drivers for interesting (really, mac) hardware?
> There's only so much that the downstream distribution has control over,
> and I appreciate that Gentoo, generally, has accepted that the state of
> the world is that rust can't easily be avoided.
No, I don't expect any of the above.
I was thinking more as a putative project manager at the start of, say, a
project to design and produce a device with embedded software. The
question would arise as to what language to program it in. Rust would
likely be a contender. But if it were up to me, I'd veto it. The
language isn't stable, doesn't have a standards body (such as ISO)
defining it, there is only one compiler, there aren't that many
competent practitioners, and so on. Add to that the difficulty of
recreating an up to date compiler if the current infrastructure
collapsed for any reason, then I think it fair to say that current users
of rust are courageous.
None of this has anything to do with Gentoo, really, it's just a
tangent.
> There are a bunch of volunteers keeping the lights on, navigating some
> of these pitfalls -- even though they themselves might actually agree
> with you -- because they represent the reality of the OSS landscape.
> ...but complaining about it here is unlikely to actually change
> anything, and only dishearten the folks who are trying to keep it all
> working. It's nicer to focus our mental energy and time on changes that
> are achievable as a project -- or specific, fixable technical issues,
> like the wedged install this started with (and the reply with direct
> information on how to fix it).
I wasn't wanting to dishearten anybody. Apologies for doing so
unintentionally.
> My $.02,
> JayF
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2025-05-02 22:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 17:07 [gentoo-user] Fragile python update is wedged Alan Mackenzie
2025-05-02 17:22 ` Pramod V U
2025-05-02 17:47 ` [gentoo-user] Fragile rust update is wedged. (Was: Fragile python update is wedged.) Eli Schwartz
2025-05-02 19:07 ` [gentoo-user] Fragile rust update is wedged Alan Mackenzie
2025-05-02 20:07 ` Eli Schwartz
2025-05-02 21:15 ` [gentoo-user] Fragile python update is wedged [Was: Fragile rust update is wedged] Alan Mackenzie
2025-05-02 21:35 ` Wol
2025-05-02 21:44 ` Jay Faulkner
2025-05-02 22:17 ` Alan Mackenzie [this message]
2025-05-02 22:21 ` Jay Faulkner
2025-05-02 21:56 ` Eli Schwartz
2025-05-04 16:41 ` Alan Mackenzie
2025-05-04 17:01 ` Eli Schwartz
2025-05-03 3:14 ` [gentoo-user] " Grant Edwards
2025-05-03 4:07 ` [gentoo-user] Fragile rust update is wedged Nate Eldredge
2025-05-11 11:54 ` [gentoo-user] Fragile python " Wol
2025-05-11 12:42 ` Dale
2025-05-11 13:26 ` Philip Webb
2025-05-11 14:52 ` Dale
2025-05-17 7:17 ` Dale
2025-05-18 12:06 ` Michael
2025-05-18 14:26 ` Dale
2025-05-11 15:14 ` Eli Schwartz
2025-05-11 12:43 ` Frank Schletz
2025-05-11 13:37 ` Wol
2025-05-11 14:55 ` Dale
2025-05-11 15:04 ` Eli Schwartz
2025-05-11 17:40 ` Wol
2025-05-11 18:06 ` Michael
2025-05-11 18:08 ` Eli Schwartz
2025-05-11 19:10 ` Wol
2025-05-11 19:47 ` Eli Schwartz
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=aBVEXQwfBwSGLw4-@MAC.fritz.box \
--to=acm@muc.de \
--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