From: Michael Orlitzky <michael@orlitzky•com>
To: "brian m. carlson" <sandals@crustytoothpaste•net>,
ezekielnewren@gmail•com,
20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks•im,
Johannes.Schindelin@gmx•de, ben.knoble@gmail•com, cb@256bit•org,
collin.funk1@gmail•com, contact@hacktivis•me,
eschwartz@gentoo•org, git@vger•kernel.org, gitster@pobox•com,
me@ttaylorr•com, newren@gmail•com, phillip.wood123@gmail•com,
pierre-emmanuel.patry@embecosm•com, ps@pks•im, sam@gentoo•org
Subject: Re: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty
Date: Mon, 22 Sep 2025 19:23:31 -0400 [thread overview]
Message-ID: <92bdf57fa8ca49159db3e3384784aa2538a3b48a.camel@orlitzky.com> (raw)
In-Reply-To: <aNHBIHXYPmS5AvpP@fruit.crustytoothpaste.net>
On Mon, 2025-09-22 at 21:35 +0000, brian m. carlson wrote:
> On 2025-09-22 at 15:59:49, Michael Orlitzky wrote:
> > There is no problem with supporting rust on Gentoo. Gentoo users build
> > from source, and rust is a problem for anyone who builds from
> > source. I'm writing this on a riscv/musl system. If there are no
> > binaries for your CPU/libc, let me tell you, it's not fun. And this is
> > like, my job. A normal person would be completely helpless.
>
> This is a problem with languages that bootstrap from earlier versions of
> themselves. It also happens with other, less common languages. GHC (a
> Haskell runtime) also has this problem and any distro that ships pandoc
> has to deal with it.
Spectacular example.
In Gentoo we support the following arches: alpha, amd64, arm, arm64,
hppa, loong, m68k, mips, ppc, ppc64, riscv, s390, sparc, and x86. We
support both glibc and musl, for 23 arch/libc combinations (we don't
support musl on every arch).
Pandoc supports: amd64, arm64, ppc64, riscv and x86, but only on glibc.
That's 5 out of 23. If you're able to use GHC 9.2 released in 2021,
that is. Otherwise it's 0 out of 23. No one "has to deal with"
anything.
Coincidentally, I am one of only a few people to bootstrap a modern GHC
on riscv/musl:
https://wiki.gentoo.org/wiki/User:Mjo/GHC_binary_packages
Knowing the amount of work involved, I can promise that if Git switched
to Haskell today, it would be our users who would have to deal with...
not having Git any more.
I agree completely when it comes to the benefits of static typing and
memory safety. (I've been writing Haskell for 15 years, after all.) But
for the time being, all of the cures are worse than the disease.
next prev parent reply other threads:[~2025-09-22 23:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 17:36 [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty Sergey Fedorov
2025-09-19 17:56 ` Ezekiel Newren
2025-09-19 18:14 ` Collin Funk
2025-09-20 8:24 ` Florian Märkl
2025-09-22 15:59 ` Michael Orlitzky
2025-09-22 16:17 ` Sam James
2025-09-22 21:35 ` brian m. carlson
2025-09-22 21:47 ` Sam James
2025-09-23 5:05 ` Patrick Steinhardt
2025-09-22 23:23 ` Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-20 8:29 Sergey Fedorov
2025-09-20 18:39 ` rsbecker
2025-09-20 19:00 ` Ezekiel Newren
2025-09-20 19:25 ` Sam James
2025-09-20 23:17 ` rsbecker
2025-09-20 23:48 ` Ezekiel Newren
2025-09-21 1:15 ` rsbecker
2025-09-21 1:24 ` Ezekiel Newren
2025-09-21 3:18 ` rsbecker
2025-09-21 16:49 ` Ezekiel Newren
2025-09-21 23:07 ` rsbecker
2025-09-21 23:42 ` Ezekiel Newren
2025-09-22 16:21 ` rsbecker
2025-09-04 14:26 Patrick Steinhardt
2025-09-19 18:41 ` John Paul Adrian Glaubitz
2025-09-22 13:01 ` Patrick Steinhardt
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=92bdf57fa8ca49159db3e3384784aa2538a3b48a.camel@orlitzky.com \
--to=michael@orlitzky$(echo .)com \
--cc=20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks$(echo .)im \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=ben.knoble@gmail$(echo .)com \
--cc=cb@256bit$(echo .)org \
--cc=collin.funk1@gmail$(echo .)com \
--cc=contact@hacktivis$(echo .)me \
--cc=eschwartz@gentoo$(echo .)org \
--cc=ezekielnewren@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=newren@gmail$(echo .)com \
--cc=phillip.wood123@gmail$(echo .)com \
--cc=pierre-emmanuel.patry@embecosm$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=sam@gentoo$(echo .)org \
--cc=sandals@crustytoothpaste$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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