Linux

47958 readers

990 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

[email protected]

On Rust, Linux, developers, maintainers (airlied.blogspot.com)

submitted 2 months ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

There's been a couple of mentions of Rust4Linux in the past week or two, one from Linus on the speed of engagement and one about Wedson departing the project due to non-technical concerns. This got me thinking about project phases and developer types.

all 6 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 2 months ago (1 children)

Talks about different developer styles, slightly interesting and not too long winded I guess, but not much about the actual situation.

I think this is still not such a great look for Rust. I had expected interfacing Rust to C to present fewer problems than it seems to. I had hoped the Rust compiler could produce object code with almost no runtime dependencies, the way C compilers can. So integrating Rust code into the kernel should be fairly painless from the C side, if things were as one would hope.

It does sound to me in the earlier post that there was some toxicity going on. Maybe it had something to do with the context being a DRM driver.

I looked at a few Rust tutorials but they seemed to take forever to get to any interesting parts. I will keep looking.

[+] [email protected] 1 points 2 months ago* (last edited 1 month ago) (3 children)

[deleted]

[–] [email protected] 2 points 2 months ago

Your point about it being a culture issue is spot on. Many maintainers who are established in the kernel have made it clear they'd rather keep the status quo and the comfort of stagnation rather than bring a new technology forward to improve the security of their systems.

If it wasn't Rust, but some other language with similar benefits, the same people would've thrown their hands in the air and complained that they're being forced to rewrite everything or some other hyperbole.

Because it's a FOSS project, for some reason it's acceptable for maintainers to be entitled arseholes who abuse anyone they personally have a vendetta against.

In any other workplace, this behaviour wouldn't be called "nontechnical concerns" it would be called workplace bullying. And as much as Linus wants to say he's working on his anger issues, he is personally one of the contributors who has set this culture of aggression and politicking as much as any other.

[–] [email protected] 1 points 2 months ago

As an aside, the DRM and its support for the supposedly superior-on-linux AMD-powered devices is atrocious. I've had my laptop since January and it's a model from 2023, but it still regularly has mega display corruption from memory mismanagement that might be improved from a certain language feature not offered in C.

[–] [email protected] 0 points 2 months ago (1 children)

"DRM" as in digital restrictions management I assume.

[–] [email protected] 2 points 2 months ago

DRM in this context (as mentioned by the other comment) is the interface between the userspace graphics drivers (Mesa, Nouveau, Nvidia etc.) and your graphics devices. It handles pretty much everything for rendering from displays to power management and memory synchronization, in a cooperative way that stops crashes due to race conditions, memory corruption etc.