144
Linux 6.14 With Rust: "We Are Almost At The 'Write A Real Driver In Rust' Stage Now"
(www.phoronix.com)
this post was submitted on 29 Jan 2025
144 points (100.0% liked)
Linux
5864 readers
340 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What is wrong with the commenters on Phoronix? There seem to be a bunch of old dudes who can't accept that C is unsafe and no amount of "skill" will prevent it from being unsafe. They look at 3 decades of unsafe C with thousands of CVEs and still think it's a skill issue.
Anti Commercial-AI license
If you think the comments about Rust are bad, you should check out any article about X11/Wayland or systemd.
Yeah, I don't understand the wayland and systemd hate. Personally, the alternatives are worse in many areas. managing services before systemd was terrible and I'm very happy it's here. Making services depend on magic comments is a terrible system IMO. Can't remember if that's upstart or rinit or whatever.
Anti Commercial-AI license
Wayland hate I at least understand. Their security model makes it not a 1:1 replacement for X11 yet, but that's what it's marketed as.
There's definitely stuff it breaks. I still miss Autokey.
Old NVIDIA gpu here. Wayland is still completely broken for me. I shouldn’t have to buy specific hardware to make my Linux work.
But that is hardly Waylands fault, be angry about Nvidia for having bare to none Linux support for decades.
And yet works fine for me in x11 where my windows and mouse both don’t run at 1fps. I hobby work with ai models and cuda, someone needs to fix it or I’m sticking with x11. I never said it was waylands fault, but given nvidia never acknowledged x11 either and it works over there maybe accepting reality about who is more likely to fix it would be good for that team.
NVIDIA is a billion (maybe trillion now?) dollar company that leaves it up to people in their free time to support their hardware on linux and you're blaming the unpaid devs, not NVIDIA?
Anti Commercial-AI license
I’m not blaming anyone. I’m stating a fact that Wayland does not work for me and that as long as that is true, an opinion that x11 is better. I don’t care who fixes it. Especially in the world of running ai models, it’s more and more important that nvidia works in your environment
A Linux user time traveling from the 90s/00s would be elated to know that one day someone could possibly have this opinion.
There are exactly 3 types of phoronix commenters:
If you open the comments on Phoronix you have already lost.
Learning that the hard way 😂
Anti Commercial-AI license
I love C and C++ and I talk to someone else who does (comp sci grad) but he's hugely biased against rust and says shit like "rust is cringe it has training wheels, just be good at C"
it's like a weird tech anti-intellectualism
It's just elitism. They think because they've suffered to learn C and have learned all the footguns of the language that they are smarter than people who haven't, so they see anything higher level than C as being a baby language for babies. 30 years ago I'm sure there was the equivalent of people who exclusively worked in assembly who thought the same about C programmers.
Isn't it exactly the point Linus was making about Rust?
The C/C++ fandom is...something else. For many, C is perfect for every use case and everything else higher level from C# to JavaScript is nothing but inefficient waste for programmers who aren't good enough for something like C lol
Technically, it is a skill issue though, but requires borderline perfection to achieve safe code. It's still a bad argument and detracts from progress in an area where it's sorely needed. Correct me if I'm wrong, but my understanding is that everything unsafe is because the logic used left something exposed where rust has rules in the language the prevents those had coding practices. C is inherently unsafe, it just doesn't have built in safe guards to keep the dev from using it wrong.
If near perfection is the minimum to achieve a goal, then it can't be a skill issue, IMO. But I agree with the rest. It's a terrible argument that keeps getting repeated, not only for C but many other places in the tech world.
Anti Commercial-AI license
Well performance is important and Rust is fast on paper afaik but idk how it works in real use cases. I don't remember seeing performance benefits on Rust compared to other languages that are not C.
There's a paper about this and with C as the baseline, Rust was 4% slower for the specific tests they ran.
In these tests, Rust is actually faster than C sometimes.
So it really does depend on the workload. However, the safety that rust provides cannot be understated. It's easy to cut corners like in C, but it's difficult to do it right. Rust provides the closest result of right and fast.
Anti Commercial-AI license
Like UI? Was that a hypothetical or a real example?
Anti Commercial-AI license
I wrote a GTK application in Rust some time ago and it was filled with macros to deal with lifetime issues. Most issues could only be solved with unsafe macros or Rc<RefCell>. The experience working with it is probably a lot better when using newer declarative frameworks, but using it with a toolkit written for C wasn't fun.
I personally prefer it for cli programs. The executables are considerably larger than C programs due to static linking, but that does mean that it works regardless of what libraries you have installed without any hassle.
Rust on top of a C/C++ lib is not fun, that's for sure. It has to setup a firewall around C which adds complexity. Using a rust native framework is better, IMO. Slint and egui are good examples thereof.
As for application size, check this out.
Anti Commercial-AI license
Yeah, I wrote two "plugins" some time ago and the Assembly implementation was shorter than the Rust implementation due to the need to convert from C ABI and back 😅.
I have taken a look at both Slint and Egui before, but they didn't seem to integrate that well with the Linux desktop last time. I just checked again and it seems like Slint has a Qt backend now which is nice. I don't really like immediate GUI frameworks, but JavaFX has so far been my favorite framework to work with so maybe I'm just weird.
And yes, I have used min-sized-rust's tricks for several of my projects, and it's very effective. However statically compiling just doesn't compare to using C and linking with the system libraries.
I found Java Swing to be the easiest GUI framework to use. Never tried JavaFX. Would you call it an upgrade?
Rust does support dynamic linking (doc, stackoverflow), but AFAIK the crate has to explicitly be configured to do so (I might be mistaken though as I've never tried it). And from what I gather the rust ABI isn't stable (which is a pity) so it's "safer" to output a cdy-lib than a dy-lib.
Maybe in the future the rust ABI will be stabilized.
Anti Commercial-AI license
It is definitely an improvement over Java Swing. One thing I really love and miss with other frameworks is how easy it is to connect properties with each other. All values are exposed as Properties and Values. Values can be listened to, mapped and used. They are similar to RXJS's Observables except that you can always get the internal value without a lastValueFrom that may fail. Properties can also be listened to, mapped, etc but their value can also be set from everywhere (RXJS instead has Subjects which can only be set from inside the constructor). It's a really easy, yet powerfull system. I have yet to find a single framework that does that part as well as it does.
And regarding Rust lack of stable ABI, even if that's resolved (and last time I checked there wasn't much interest from within). The main Linux distributions will still have to ship the Rust stdlib as a shared library to be able to reliably depend on it being available.
I do wonder if it would be advantageous to write a safe wrapper around the C and C++ standard libraries. It would mean being able to use it's functionality, while being relatively sure that those dependencies are available while only having to add a little extra code (and thus size) to the executable for the wrappers.
Someone said Rust wasn't very good at UIs in terms of performance. Though I don't remember where it was published.