From: Michael Orlitzky Date: Mon, 22 Sep 2025 23:23:31 GMT Subject: Re: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty Message-ID: <92bdf57fa8ca49159db3e3384784aa2538a3b48a.camel@orlitzky.com> In-Reply-To: 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.