I'll be doing a video on the Rust linux stuff, but the short story is Linus needs to put his foot down and decide what's happening with Rust, the way things are going can't be allowed to keep happening.

Either say you changed your mind Rust is not happening and tell the Rust fans to piss off and shut up about it, or tell the people trying hard to stop Rust to grow up and learn to work as a community. Sitting around watching these fights happen over and over again is a waste of everyone's time.

@BrodieOnLinux
Before Rust came out I never heard of this hardcore programming language fanboy bullshit. Yeah there were people that preferred certain languages over the other but the absolute hate towards people that use one language you particularly don't like, where the hell did that stem from?
@BrodieOnLinux
If you don't like the language and project is written in, then don't contribute to it. It has no relevance to you if you're not a developer on it.
@liamolua A lot of that comes from Rust being a language that spawned during the age of social media, from the very first day you could make your entire online persona about one language. You could have talked about nothing but C with your colleagues but it didn't let you reach the same level of audience.
@BrodieOnLinux
This makes a lot of sense actually.
@liamolua @BrodieOnLinux well, C simply had no competition at the time. Rust is now a competitor to both C and C++ so of course it became controversial
@liamolua @BrodieOnLinux Look at the lack of tolerance in recent decades for those who don't share one's political/cultural choices. People have developed personalities that tend to be pugnacious (see what I did?) about everything. Every disagreement becomes a hill to die on, and nobody remembers how to compromise.

@BrodieOnLinux
While I agree that torvalds picking any side is probably better than nothing, I honestly think that backing out of rust at this point is a mistake.

It be basically cementing the idea that the Linux kernel development can literally never change and that any attempts to change it will be fiercely resisted. Plus there are already drivers and such written in rust. Throwing all of that now would be a huge waste.

@enthusiast101 As it currently stands those drivers basically don't exist, they will never be merged into the upstream kernel. I want Rust to actually be brought into the kernel but as it stands nothing is going to change.
@BrodieOnLinux But isn't implied with his approval of Rust that the second alternative is already the one he chose?
@BrodieOnLinux
The day he does a lot of people will leave the kernel.
Which side's, not sure. But it's kinda inevitable.
@BrodieOnLinux Agreed. He can't just say another language is in and then walk away. This latest drama is clearly the old devs don't want _any_ other languages.

@BrodieOnLinux true. Did they even reach something in that dma coherent allocator thread? I've read most of it and it seems like it went nowhere.

The Rust maintainer burned out amd Greg/Linus said nothing besides "stop making dramma". Yea, okay, BUT WHAT ABOUT RUST ABSTRACTIONS, DAWG?

@BrodieOnLinux like, this feels like a very important topic to reach consensus on: we either do or do not allow Rust abstraction (opposed to always accessing C API directly). I can't imagine moving R4L forward without picking something.
@BrodieOnLinux All and everything I heard about Rust and the Kernel was steaming hot drama coming from Rust fanboys and people trying to bring in I there Kernel.