Rust in Linux's Kernel 'is No Longer Experimental'https://events.linuxfoundation.org/linux-kernel-maintainer-summit/At the invitation-only Linux Kernel Maintainers Summit here, the top Linux maintainers decided, as Jonathan Corbet, Linux kernel developer, put it, "The consensus among the assembled developers is that Rust in the kernel is no longer experimental — it is now a core part of the kernel and is here to stay. So the 'experimental' tag will be coming off." As Linux kernel maintainer Steven Rosted told me, "There was zero pushback."This has been a long time coming. This shift caps five years of sometimes-fierce debate over whether the memory-safe language belonged alongside C at the heart of the world's most widely deployed open source operating system... It all began when Alex Gaynor and Geoffrey Thomas at the 2019 Linux Security Summit said that about two-thirds of Linux kernel vulnerabilities come from memory safety issues. Rust, in theory, could avoid these by using Rust's inherently safer application programming interfaces (API)... In those early days, the plan was not to rewrite Linux in Rust; it still isn't, but to adopt it selectively where it can provide the most security benefit without destabilizing mature C code. In short, new drivers, subsystems, and helper libraries would be the first targets...Despite the fuss, more and more programs were ported to Rust. By April 2025, the Linux kernel contained about 34 million lines of C code, with only 25 thousand lines written in Rust. At the same time, more and more drivers and higher-level utilities were being written in Rust. For instance, the Debian Linux distro developers announced that going forward, Rust would be a required dependency in its foundational Advanced Package Tool (APT).This change doesn't mean everyone will need to use Rust. C is not going anywhere. Still, as several maintainers told me, they expect to see many more drivers being written in Rust.
whatever, im checking out before 2030 anyway, clown world is too much for me
what they are trying to do?
>>107538423make the linux kernel even more corpo
>>107538423force the kernel into HRT
>>107538433>>107538448I was talking about the Indians in the video.
>>107538467they saw a white woman
>>107538467RETARD
>they're here to stayAnd now they've started going mask off about it.See the DMA subsystem demanding all future drivers be written in Rust and disallowing C.Same with Debian ports.
>>107538467That's the linux kernel dev team, retard.
>>107538278Embrace, Extend, Extinguish.Microsofts plan to force people to Win 11 by ruining Linux. 4% marketshare is too muchRustoids could have just forked the kernel and replace whatever they want with Rust. No discussion necessaryDistros can then choose to plug and play their Rust Kernel into DistrosBut noooo.... We attack the Kernel directly. This is on purpose
>>107538554>demanding all future drivers be written in RustI'll take "things that never happened" for $200, Alex.
>>107540428https://lwn.net/SubscriberLink/1050174/63aa7da43214c3ce/>It was still perhaps surprising, though, when Airlie (the DRM maintainer) said that the subsystem is only ""about a year away"" from disallowing new drivers written in C and requiring the use of Rust.
>>107538554who are "they"? (always love the [non-]answers i get for this one kek)>>107540778this reminds me of a comment i made more than (holy fuck) a year and a half ago.https://desuarchive.org/g/thread/100447468/#q100448647follow that exchange to the end for maximum laughs ;);)that coping /g/eet is still with us btw. hopefully it's not you lol.but in any case, dave went overboard there, even if he's just making a point.
>>107538278apologize
