Rust For Linux Has A New Linux Kernel Policy

After the Rust for Linux kerfuffle, something needed to changed and one change that went in places was a new Rust For Linux policy on how to deal with upstream maintainers, who's responsible for changes, etc.

==========Support The Channel==========

==========Resources==========

=========Video Platforms==========

==========Social Media==========

==========Credits==========
🎨 Channel Art:
Profile Picture:

#Rust #Linux #LinuxKernel #OpenSource #FOSS

🎵 Ending music
Track: Debris & Jonth - Game Time [NCS Release]
Music provided by NoCopyrightSounds.

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.

[SSquirrel]

If Linus has said all this a few weeks ago, we wouldn't have lost some folks from the kernel

[basilefff]

People in this comment thread who think drama is Rust exclusive, do you even watch this channel? Wayland drama is at this point is only just short of being a telenovela.

[AlexMax]

Hats off to both this policy and Linus coming down hard on Hellwig. Hopefully communication between the two projects will be more productive going forward.

[muha]

I think the entire Linux kernel should be re-written in a more enterprise language, like Oracle Java™

[laundmo]

ik making videos takes some time but its kinda odd to see a video on this which doesn't mention Linus response to The Drama and especially what he considers this situation to be (just another user of the subsystem, with the same overhead as any C user of the subsystem).

[evlogiy]

That whiteboard sketch of the Rust logo is... artistically unique. I hope the Rust Foundation doesn’t come after you for trademark infringement! 😂

[vicca]

Now let's hope some maintainers stop going "I don't want anyone touching my code with their infectious foreign code".

Somewhat as Linus said "If you don't want to touch Rust code, fine, but you don't get a say in how Rust code uses your code".

[luketurner]

13:58 If I may rephrase the question a bit: Are companies involved? yes. Involved in what? yes. Which things exactly? yes

[IchikaZou]

These is the reason I still use Linux over *BSD despite all the drama. Linux grow and adapt from its mistakes.

[theftking]

Honestly everyone involved in rust needs to be put in jail. I get that rust is all about safety but I'm all about f*cking danger so it's just not compatible.

[haithem]

rust on kernel?
writing means rethinking implemetations. new developers might discover new ways to optimize and solve problems.
which ultimately improve the kernel.

it doesn't matter if its rust or zig or c++.
i just love when developers rethink how things work and maybe make a better wheel.

[LoopyLucy]

As someone who knows very little about the linux kernel and in-fact has no idea what Rust actually is, It's very, very amusing to me that something called "Rust" is making something fall apart.

[TissueCat]

I think the kernel should only have stable, time-tested languages, like cobol

[desktorp]

"Not monolithic but a bunch of subprojects within a monolithic package"

The word you are looking for is Xenolithic.

[MonochromeWench]

A big improvement but no doubt will not be good enough for the 'no rust" types. C code being allowed to break rust temporarily is huge and is something I thought was needed in policy to reduce the amount of impact on existing C Kernel Maintainers. If people can cooperate then there should be no problems. Before a breaking change occurs ideally the C Maintainer would notify the rust Maintainer it's going to happen but some people refuse to cooperate so maybe I'm being too idealistic

[AubyAutumn]

Lmao I said this on another video but good thing Linus is the one driving decisions on linux with this.

[szaszm_]

Now we just need Linus and/or Greg KH to sign off on this policy.

[callofbrokendreams]

Many dont seem to realise but it have half a century of C, new learners arent as excited to learn C as some newer options. C is a language of an entirely different era and philosophy, though it may still be strong and widely used we cant deny that C is trailing behind in some places. Also everything has a lifespan, C included. While to casual eye there is no problem but internally C is dying not as in userbase but in innovation and the ease it provides. One thing about programming language is any language can be used for anything, only factor being how easy it is in a certain one than the other. If rust is good it will catch if it isnt it will die same with C, but nothing happens overnight so we have yet to see what will happen but honestly me personally i want C to rest.

Also in topic of linux, it is foss driven on developers passion and from what i have seen it seems like what you would expect of old people being stubborn, it is heartbreaking to see something that you worked on your entire life, had your career built on getting replaced. But still linux is driven by developers passion, injecting new blood on something as critical is very necessary and how many young people have seen enthusiatic to learn C or C++ ir java and such, not many. Languages liek rust and zig were specifically made to address issues with C and C++, so they address many key vulnarabilities of C and C++. If we start gatekeeping new innovations like this than we r just moving ourselves to a large problem that could be easily avoided.

[TheLinuxCast]

Rust/anti-rust people are more annoying than the Arch and GNU/Linux people

[davidfrischknecht]

Since I'm not a kernel developer, I couldn't care less which language the kernel is developed in as long as it works properly.