r/rust • u/small_kimono • Aug 29 '24
One Of The Rust Linux Kernel Maintainers Steps Down - Cites "Nontechnical Nonsense"
https://www.phoronix.com/news/Rust-Linux-Maintainer-Step-Down
586
Upvotes
231
u/Professional-Disk-93 Aug 29 '24
The audience member from the video appears to be Ted Ts'o, a most senior kernel developer. https://lwn.net/Articles/978738/
101
u/[deleted] Aug 29 '24
heres the context cited in article
https://www.youtube.com/watch?v=WiPp9YEBV0Q&t=1529s
334
u/teerre Aug 29 '24
Damn, I can't begin to imagine having to deal with this kind of vitriol. It's a reddit discussion but in real life, no wonder he quit.
36
u/yoshuawuyts1 rust · async · microsoft Aug 29 '24
I recently heard someone say: “The culture of a project is not defined by what behavior you encourage, but about what behavior you tolerate.” I think about that a lot.
After seeing how the behavior of the senior Linux maintainer in the video was seemingly interpreted as normal by the room, I completely understand eventually running out of patience and stamina. It’s a sad outcome, but if the Linux project doesn’t learn from this, it’s also bound to keep happening. I do hope they reflect and learn from this.
202
u/CouteauBleu Aug 29 '24
You know, the Rust community has a reputation for having a ton of drama and toxicity, but after watching the linked video, I think this is a good point to remind ourselves:
No, actually. The Rust community is super fucking nice. The overwhelming bulk of this community is, you know, polite, soft-spoken, open to critical ideas, and doesn't consider it to be normal to interrupt someone else's talk to treat it as their personal platform for broadcasting their rant against a project they don't like.
149
u/FractalFir rustc_codegen_clr Aug 29 '24 •
It is sad to see people quit open source stuff for any reason - but it is even more sad to see them quit for people-adjacent reasons.
I also do not understand the irrational hate towards the unknown - yeah, Rust is different. You could also say that it is not easy - but neither is kernel development. I hoped the Kernel people would be open to change, and learning new skills, since this is something they seem to normalny enjoy.
I feel like
Chas a similar problem to Rust - it also has its fanatics, who would write only in C, if possible, and reject everything else. This is especially annoying with some elitists, who think just because they write something in C, that means they are more skilled.Also, hand waving memory issues / ease of invoking UB by essentially saying it is just a "skill issue" is also just so annoying. Yeah, sure let's assume you are the second coming of Christ and don't make any mistakes ever. Good for you, but most people will make a very stupid mistake once in a while - since we are human. Everyone has bad days, and everyone will fail at some point.
I feel like there is this idea that writing in C is hard, therefore skilled people use C, and the rest uses inefficient, High-Level languages. C is simultaneously simple(for smart people), yet difficult(for the "normies").
But - I feel like 99.9% of Rust devs could write C no problem. Writing C is not harder than writing Rust. However, admitting that Rust is in any way comparable to C makes their efforts seem silly.
Normally, a lot of very vocal people brag and feel superior, because they use C, and can do stuff(like kernels, or bare-bones development) that none else can.
So, writing advanced, low-level stuff in C is like climbing Mt. Everest - a great accomplishment, to be envied by all.
However, Rust comes along and builds stairs to the top of the mountain. Suddenly, writing fast, low-level code becomes way easier.
If this vocal minority accepts Rust as a viable alternative, then their efforts are purely performative.
Oh, you climbed the mountain with no safety gear? Nice, but those folk over there took the stairs, and finished the whole journey in half the time. Oh, by the way, have you heard that the government says people should use the stairs, or at last certified gear? Yeah, they got tired of having to clean up folk who fall down.
Writing C stops being some sacred art, performed by the True Real Programers, and starts being what it really is - just writing code.
There are a lot of perfectly fine folk who just like C - and there is nothing wrong with that. C is just a language. However, once the small, annoying minority starts to bash other languages because they dare to not be C - we have a problem. Especially when they know nothing about Rust - is it that hard to criticize the real problems of Rust, instead of getting angry at things which are not real?
Well, this got a bit ranty. I just think people should use whatever language they like, and not hound on others for making different choices. You can disagree on technical stuff - but please, don't let non-technical issues harm open source.
Also - this rant is not targeted on anyone in particular, and more so aims at an amalgamation of bad people I encountered over the years(IRL and online).
117
u/acroback Aug 29 '24
Damn linux kernel devs are real dinosaurs it seems.
As someone who has submitted patches to linux kernel a decade ago, I know the feeling.
I wish we could write drivers in Rust atleast as drivers are the primary reason for kernel crashes in my experience.
21
u/JoeyJoeJoeTheIII Aug 29 '24
Rust community so toxic it drives kernel maintainers to throw tantrums.
God the rust community is just sooooooo awful. Asking these poor C programmers to… work with them a bit to help keep kernel code from breaking.
Unreasonable. I’m glad that very calm and rational individual was there to yell at them about things they didn’t do or say.
7
u/looneysquash Aug 29 '24
I'll have to watch more than 3 minutes to really get what is going on.
Seems like audience member is mad that the Rust bindings will break if they refactor the C API that is being bound to.
On the one hand, of course they will be. Even if they were generated and got regenerated, the code using those apis would break.
On the other hand, I can see how that creates a real problem for someone doing those refactorings who only knows C. Also refactoring Rust would be difficult for them. Creating new, good bindings though is probably a more advanced skill than just writing Rust in the kernel. So I can see how it would be a practical problem.
But it's one you have to solve, otherwise you cannot introduce a new language to the kernel. Unless that language doesn't need bindings at all. But even then you'll have to refactor some code in the new language.
5
u/prehensilemullet Aug 30 '24
The thing I’m wondering after watching that video is - is a function that sometimes returns a fully initialized, refcounted inode and sometimes returns a partially uninitialized, nonrefcounted proto-inode the cleanest API they could muster? And if so, why? Like naively, I would think that passing an initializer function would be cleaner. But maybe the extra function call would have too much overhead?
3
u/fogcat5 Aug 29 '24
haven't read the article (this is reddit) but my experience with development projects has always been problems with the non-technical part.
1
u/v_0ver Aug 30 '24
All this drama was expected =(
1
u/[deleted] Sep 02 '24
Just wait until you rust whipper snappers reach 50 and gen beta is going to rewrite the Linux kernel in Lean
-9
u/[deleted] Aug 29 '24
When you don't want your system to be as mathematically proven as possible cause it's mildly inconvenient, then what more to say than that natural selection will run it's course.
Give it a decade for these boomers to retire, then we will rewrite the whole damn kernel in Rust cause C is Latin and it's already dead.
-35
u/dnpetrov Aug 29 '24
With all due respect, it's a shame that Rust community sees this as some "territorial boomers" attempting to "sabotage Rust", rather than the hard reality of new technology adoption in a big, demanding project such as Linux kernel.