this post was submitted on 21 Sep 2024
322 points (98.8% liked)
Linux
48315 readers
700 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 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem is that the Linux kernel is monolithic so introducing rust into it does have certain repercussions about downstream compatibility between modules.
Right now the rust code in the kernel uses c bindings for some things and there's a not-insignificant portion of C developers who both refuse to use rust and refuse to take responsibility if the code they write breaks something in the rust bindings.
If it was pure C there would be no excuse as the standard for Linux development is that you don't break downstream, but the current zeitgeist is that Rust being a different language means that the current C developers have no responsibility if their code refactoring now breaks the rust code.
It's a frankly ridiculous stance to take, considering the long history of Linux being very strict on not breaking downstream code.
Rust developers are fine with C bindings changing, they just want that to be communicated to them by the C developers before they break.
A valid point. But the result is that over a pretty short period of time. These C developers will find delays in how quickly their code gets accepted into stable branches etc. So will be forced to make clear documentation into how the refactoring effects other elements calling the code. Or move on altogether.
Sorta advantageous to all and a necessary way to proceed when others are using your code.
Yeah sorry, c/c++ guy here.
I get that rust is the new shiny.
But now it means changing any potentially bound c function means I need to be fluent in a language I barely heard of before this year and has a syntax that makes c# look normal.
So, how about no?
You just have to document your code. Nothing more.
No, you just have to talk to the people who are fluent in rust.