Google recently rewrote the firmware for protected virtual machines in its Android Virtualization Framework using the Rust programming language and wants you to do the same, assuming you deal with firmware.
In a write-up on Thursday, Android engineers Ivan Lozano and Dominik Maier dig into the technical details of replacing legacy C and C++ code with Rust.
“You’ll see how easy it is to boost security with drop-in Rust replacements, and we’ll even demonstrate how the Rust toolchain can handle specialized bare-metal targets,” said Lozano and Maier.
Easy is not a term commonly heard with regard to a programming language known for its steep learning curve.
Nor is it easy to get C and C++ developers to see the world with Rust-tinted lenses. Just last week, one of the maintainers of the Rust for Linux project - created to work Rust code into the C-based Linux kernel - stepped down, citing resistance from Linux kernel developers.
“Here’s the thing, you’re not going to force all of us to learn Rust,” said a Linux kernel contributor during a lively discussion earlier this year at a conference.
Here’s the thing, you’re not going to force all of us to learn Rust
That seems like a poor attitude imo.
I mean aren’t they forcing everyone else to learn C/C++ otherwise? If we follow that logic, at least
I guess you can argue it’s already written in C. So that was always a requirement.
That way we’ll just find maintainers went near extinct over time, just like COBOL developers that are as rare as they are expensive. Only Linux kernel isn’t a bank, and maybe will not have as much money to pay to rare developers capable of maintaining C codebase
That seems like a poor attitude imo.
Why do you believe that forcing something onto everyone around you is justifiable? I mean, if what you’re pushing is half as good as what you’re claiming it to be, wouldn’t you be seeing people lining up to jump on the bandwagon?
It’s strange how people push tools not based on technical merits and technological traits, but on fads and peer pressure.
It is literally being pushed for its technical merits and traits.
Memory safe code with comparable performance in the kernel seems like an absolute no brainer.
Also if you watch the video all he’s asking for is consistent interfaces for the file systems. He’s not even trying to get them to use rust. And the guy starts screeching about how he’ll code however he wants.
Is it wrong to expect a consistent and well documented interface?
Pretty sure C is actually being pushed against its technical merits here.
It’s wrong to force it. Most choices in history don’t end up with the best one being used. Beta was better than VHS for example. Rust people are very bad at convincing others to try it, and objectively many people just don’t want to or don’t like it for various reasons.
Personally I highly dislike the syntax. People like familiar things, and to me it’s just too different from C++.
If anything I think Swift will be an easier sell when the speed and cross-platform issues are solved.
Oh jeeze, you have no idea. You can watch it yourself: https://youtu.be/WiPp9YEBV0Q?si=b3OB4Y9LU-ffJA4c&t=1548
That timestamp is about where the audience member (a maintainer of ext4 and related utilities) starts speaking. The “here’s the thing” quote is around 28:40.
If the linux kernel had any real budget to speak of, they could hire rust experts to maintain the rust code. But the “linux” foundation spends 2% of its budget on Linux, this is the situation you end up with.
I believe that’s incorrect. The reporter who started this rumor either misunderstood the meaning of the chart or was lying through his teeth. I’ll find the original source and share it here later.
This is the actual source. If you simply scroll through it, you’ll see they’re investing in many things that move the Linux ecosystem forward. Open standards, open hardware, security in the software stack, providing for latest market needs, keeping an eye on legislation that could affect Linux, staying in touch with important entities in the industry, and so on.
Scroll down near the bottom and you’ll find where the reporter got their information from. It’s an expenditure chart and, sure enough, it says “Linux Kernel Support 2%” Note, however, that it also says:
- Community Tooling 5%
- Training and Certifications 7%
- Project Infrastructure 9%
- Project Support 64% (!)
Note that it doesn’t say how any of them is further divided. Remember all the things I mentioned earlier? All of that is value for Linux as a whole.
Software projects aren’t just about programming the big thing. Working on a large project will show you this. Could the foundation spend more on Linux? Maybe. But saying they only spend 2% on it is disingenuous.
The reporter doesn’t mention this in his clickbait piece, either because he doesn’t get it in the first place, or more likely because he just wants to push his views.
This is yet another example why Lunduke isn’t a credible source of news.
A valid point tho. Generally it is difficult to ask everybody to learn a new language.
It would be a valid point if he weren’t literally speaking over the people trying to tell him that they’re not demanding he learn Rust: https://youtu.be/WiPp9YEBV0Q?si=b3OB4Y9LU-ffJA4c&t=1548
I mean, I work as a software engineering and if I’m not doing continuing ed, be it about architecture, storage, or new languages, I’m going to be of less value in the marketplace. I’ve learnt languages I didn’t particularly want to in the past for work (though I generally came to tolerate or even like some of them. Not lua, though; lua can go to hell).
If Rust truly is the better, safer option, then these people are holding everything back.
It’s not a question of what’s the better option. In reality we have a lot of software that already exists and works, and you can’t replace it all in bulk at the same time. So the question is whether the implementation of Rust makes logistical sense, given the difficulties of maintaining currently existing software while replacing some parts of it.
C/C++ is the bedrock of our modern civilization in some ways more fundamental than actual bedrock, the first step in getting any OS running is making it run C and after that you are basically done, it’s not surprising that developers resist, if nothing else it’s a common language, and standards are hard to change on the best of days. This isn’t just learning a language, it’s a complete paradigm shift.
“learn Rust” in this case is learn it to a level where all of the little behaviour around cross language integrations are understood and security flaws won’t be introduced. Expert level.
It’s not “I did a pet project over the weekend”.
