what is wrong with rust and linux????
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
What is wrong with us?!
The PrimeTime
111.4k views
Linus x Linus - Is AI A Bubble?
ThePrimeTime
37.4k views
What even is Quantum Computing?!
ThePrimeTime
75.4k views
What even is an AI Agent?! (The Standup)
ThePrimeTime
91.9k views
Why is the Rust Compiler So SLOW?
ThePrimeTime
98.2k views
Zig and Rust in Production (ft. Matklad)
ThePrimeTime
93.2k views
PewDiePie IS RUINING MY LIFE
ThePrimeTime
436.5k views
Linux Dev on Rust, OSS and Rewriting SQLite
ThePrimeTime
83.9k views
PEWDIEPIE USES LINUX???
ThePrimeTime
715.5k views
Linux Is Obsolete
ThePrimeTime
184.8k views
Top Comments (10)
FYI the guy that was being disrespectful and disruptive to the presenter maintains the ext4 filesystem code
Let's just make everyone unhappy, remove rust from the kernel but force the C guys to actually document their code.
I think the reasonable compromise is for both sides to come together and work on rewriting Linux in TypeScript.
Reminds me of the time that blender guy gave a presentation to the blender community about how a UI overhaul was desperately needed. The amount of nerdrage was immense. Yet the blender UI is actually pretty decent now as a result. So hey, let people talk.
While I'm not a rust guy, there was no reason for those rust devs to be treated that way
This goes beyond Rust versus C. This is about accurately documenting what a function does. Rust needs this information so it can be encoded in the type system, but knowing this information in the first place benefits everyone. I say let the Rust developers cook and properly document the interfaces that the C developers failed to.
The way he was talking at the beginning sounds like he knew a potential storm was coming and was nervous...or just gets nervous speaking in front of crowds.
Presenter: "I am now going to talk about how effective Rust is for writing source code" Linux Foundation: "So you have chosen death..."
"I am too busy to document my interfaces" is a weird hill to die on.
This is how i feel when your company or team hires new people and the new people start pushing a new tech stack because it will solve all the current issues, while all the experienced engineers have seen this a hundred times and know that a new stack, language etc will just engineer new problems (which is impossible to forsee). Ultimately, everyone wants the best result, its just difficult to navigate the approach when you have two or more groups that have a lot of experience and background knowledge in their own tooling.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
FYI the guy that was being disrespectful and disruptive to the presenter maintains the ext4 filesystem code
Let's just make everyone unhappy, remove rust from the kernel but force the C guys to actually document their code.
I think the reasonable compromise is for both sides to come together and work on rewriting Linux in TypeScript.
Reminds me of the time that blender guy gave a presentation to the blender community about how a UI overhaul was desperately needed. The amount of nerdrage was immense. Yet the blender UI is actually pretty decent now as a result. So hey, let people talk.
While I'm not a rust guy, there was no reason for those rust devs to be treated that way
This goes beyond Rust versus C. This is about accurately documenting what a function does. Rust needs this information so it can be encoded in the type system, but knowing this information in the first place benefits everyone. I say let the Rust developers cook and properly document the interfaces that the C developers failed to.
The way he was talking at the beginning sounds like he knew a potential storm was coming and was nervous...or just gets nervous speaking in front of crowds.
Presenter: "I am now going to talk about how effective Rust is for writing source code" Linux Foundation: "So you have chosen death..."
"I am too busy to document my interfaces" is a weird hill to die on.
This is how i feel when your company or team hires new people and the new people start pushing a new tech stack because it will solve all the current issues, while all the experienced engineers have seen this a hundred times and know that a new stack, language etc will just engineer new problems (which is impossible to forsee). Ultimately, everyone wants the best result, its just difficult to navigate the approach when you have two or more groups that have a lot of experience and background knowledge in their own tooling.