this post was submitted on 17 Jul 2026
165 points (96.1% liked)

Linux

66538 readers
828 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] fubarx@lemmy.world 43 points 4 days ago (7 children)

So many system bugs are because of unclear memory ownership, buffer overflows, and race conditions. C/C++ don't help you avoid any of these footguns. Any other system that relies on GC is non-deterministic and prone to mystery hiccups, which is why OS and driver tech has been pretty much the same foundation since the 70s.

Rust lets you avoid 2 of those 3 issues (thread race conditions are still a thing). And being compiled, instead of interpreted bytecode means you can get reasonable performance on smaller machines. No wonder these OS guys are so excited.

[–] BartyDeCanter@piefed.social 16 points 4 days ago

Yup. Most of my career has been working on embedded realtime software, so interpreted languages are right out and really only C and a subset of C++ are available. I’ve now been using Rust in that way for about nine months now and while the syntax is sometimes silly feeling, being able to not worry about some many other issues has made development much better.

load more comments (6 replies)
[–] HaraldvonBlauzahn@feddit.org 91 points 4 days ago (1 children)

Kroah‑Hartman consistently framed language choices in terms of reviewer workload rather than developer convenience. Linux has "over 5,000 developers" but "about 150 core maintainers that review the majority of the code," a skew that drives his priorities. "We optimize for reviewers. We don't optimize for developers because we have a lot of developers," he said, suggesting Rust's ability to enforce locking and lifetime rules at build time means reviewers can spend their limited bandwidth on logic rather than bookkeeping: "If it builds as a reviewer, I know it's OK. I can look at the logic."

That's a great point. Living open source code must be readable and maintainable. Rust is an excellent match for that.

load more comments (1 replies)
[–] HiddenLayer555@lemmy.ml 23 points 4 days ago* (last edited 4 days ago) (2 children)

Don't know about "fun again" but definitely a lot less nervewracking and paranoia inducing.

[–] asdfasdfasdf@lemmy.world 9 points 4 days ago

I find Rust extremely fun

[–] thingsiplay@lemmy.ml 12 points 4 days ago

It is hard to think in and see through the eyes from a Kernel core maintainer, if you don't do this kind of stuff at this level. Instead enforcing style guides, looking for edge cases and unexpected issues because C allows to do anything must be terrifying. Part of this "nonsense" goes away using a language that is designed to handle this better. And you know, learning a new language with features you always wanted to have in C might be exciting too, I don't know. I can imagine Rust being more fun than C in the Kernel for some, so this is not a wild take or anything like that.

I think the most exhausting part of Rust was two fold: a) the language was not designed to be used in the Kernel, they needed to update and discuss after real world usage, and b) the push back from C developers who either didn't understand Rust or think its bad for the Kernel. The childhood illnesses of Rust in Linux is seemingly over.

[–] yogthos@lemmy.ml 9 points 4 days ago (8 children)

I've got a non trivial project in Rust, and it takes like 5 min to compile on my machine. Personally, I don't know how anybody can call this fun. I find it insane to have to wait minutes to see the changes and to iterate. And like sure you can break shit up into crates to speed up compilation, but to do that you already have to have a design you're happy with and that's stable.

[–] eldavi@lemmy.ml 18 points 4 days ago* (last edited 4 days ago) (8 children)

I find it insane to have to wait minutes to see the changes and to iterate.

i did devops between 2015 & 2025 and got used to the cadence of waiting between 15 & 180 minutes for testing/production pipelines to finish vetting the work i submitted to them.

i went back to doing IT last year and setup similar pipelines to update the code base my predecessor left behind and my new boss expressed the same consternation about waiting for your changes to iterate.

i'm thankful for it because it gives me 30-ish minute windows to browse and annoy people on lemmy throughout the day. lol

[–] trem@lemmy.blahaj.zone 9 points 4 days ago (5 children)

5 minutes sounds like way too much, unless you mean a fresh compile. But then you shouldn't need to wait that long between changes, since incremental compilation should kick in then.

And like sure you can break shit up into crates to speed up compilation, but to do that you already have to have a design you're happy with and that's stable.

I mean, if you have your modules structured in a tree structure and with proper visibility, then it isn't a particularly big leap to put it into a separate crate. You just move the files, maybe fix some visibility modifiers still, and then a bit of boilerplate to add it to the workspace.

It's only really when you're publishing to crates.io, that you don't particularly want to keep changing the names/scopes of the crates, as they'll stick around on there for the foreseeable future.

load more comments (5 replies)
[–] asdfasdfasdf@lemmy.world 7 points 4 days ago* (last edited 4 days ago) (12 children)

Five minutes with build cache? Or from cold build?

With cache, then there's almost certainly something wrong with your computer or project.

Also... you aren't building with --release every time are you?

load more comments (12 replies)
[–] iByteABit@lemmy.ml 6 points 4 days ago (1 children)

mold and sccache help a lot with the compile times

[–] yogthos@lemmy.ml 6 points 4 days ago

I recall looking at mold, but it didn't end up helping much in my case. And haven't looked at sccache, that might actually help if it can cache compilation incrementally in an intelligent way.

load more comments (4 replies)
[–] anon_8675309@lemmy.world 5 points 3 days ago (10 children)

Rust would be better if the rust community wasn’t so up everyone’s ass about using rust.

[–] HaraldvonBlauzahn@feddit.org 11 points 3 days ago

Attacking the messenger because you don't have any good argument against the message?

This is the Linux kernel project, one of the technically most conservative projects in the FLOSS community.

load more comments (9 replies)
load more comments
view more: next ›