122
Rust Coreutils cp Ended Up Breaking Ubuntu Image Builds With Latest Incompatibility
(www.phoronix.com)
this post was submitted on 04 Jul 2026
122 points (90.1% liked)
Linux
66392 readers
377 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It is definitely easier.
Don't try and tell me cargo is not easier than fucking around with the C/CPP build slop I've had to screw around with over the years.
The coreutils license is bullshit but let's not pretend languages have not improved in 50 years.
Yeah, the only real issue I have with the “rewrite it in Rust” approach is the absolute plague of permissive licensing. It is much easier to write safe, correct code in Rust.
I think it depends on the project, when writing cp you're not really messing around with libraries so good ol make is fine
Cargo != Rust
There is no word in which the borrow checker is easier to deal with than C.
I think responding to borrow checker errors is easier than debugging some random segfault
Also I don't separate the language and it's build system. I have to use it to write the language it's an entire kit.
Part of c/cpp problem is it's build system and dependency story just serves to get in my way instead of letting me write code. The syntax is irrelevant when I'm fucking with some auto conf script because the version on my machine is 0.01 versions different.