Re:Git: Introduce Rust and announce that it will become mand...
by JoshTriplett on Saturday September 20, 2025 @11:02AM
(#45313970)
Rust can't support a platform when that platform's vendors just provide a proprietary C compiler and nothing else (no LLVM, no GCC). Perhaps someone could reverse-engineer it, but ultimately a platform with zero support from any FOSS toolchain is unlikely to get Rust support anytime soon.
[ Parent
| on HN ]
Re:Git: Introduce Rust and announce that it will become mand...
by jen20 on Saturday September 20, 2025 @12:19PM
(#45314659)
Furthermore, how could it without the donation of hardware, licenses and so forth?! This is a problem entirely of the proprietary platforms making, and it should be their customers problem for having made a poor decision.
Re:Git: Introduce Rust and announce that it will become mand...
by kazinator on Saturday September 20, 2025 @12:32PM
(#45314820)
Reverse that: "C can't support a platform when that platform's vendors just provide a proprietary Rust compiler and nothing else".
Re:Git: Introduce Rust and announce that it will become mand...
by Yoric on Saturday September 20, 2025 @03:05PM
(#45316299)
Seems to me that that is equally true and doesn't remove any validity from the argument.
Re:Git: Introduce Rust and announce that it will become mand...
by kazinator on Saturday September 20, 2025 @06:42PM
(#45318258)
OK:
"C can't support a platform when that platform's vendors used to provide a Rust compiler, and now they don't provide any compiler."
That must still be valid.
Re:Git: Introduce Rust and announce that it will become mand...
by JoshTriplett on Saturday September 20, 2025 @11:51PM
(#45319906)
It's unclear what point you're trying to make here.
Proprietary platforms with proprietary-only toolchains are bad, for a wide variety of reasons. Open toolchains are a good thing, for many reasons, including that they can support many different programming languages.