karolherbst š§ š¦ (@karolherbst@chaos.social) "MAINTAINERS: Remove myself"
(chaos.social)
from reallyzen@lemmy.ml to linux@lemmy.ml on 15 Feb 09:49
https://lemmy.ml/post/26038917
from reallyzen@lemmy.ml to linux@lemmy.ml on 15 Feb 09:49
https://lemmy.ml/post/26038917
Following the R4L debacle āyou are cancer, you are the problem, we are the thin blue lineā, another maintainer steps down from the Linux Kernel
threaded - newest
itās a shame it has come to this. there needs to be some tough conversations on how the Linux kernel wants to be run over the next 5 years
Yup. But based on Linusā response to marcanās concerns, it sounds like Linus just wants to ignore the problems.
Yeah, this looks like trying to avoid conflict by shutting down a person pushing back against bad behavior, instead of trying to mediate the situation to come to a just resolution. Itās shallow and gross and not sustainable.
Maybe heās not American? Isnāt that just an American thing?
Linus is definitely not American. That is no excuse he way he just ignored the dma maintainerās behavior and that is no excuse for why nobody in leadership did or said anything even after the connotation of the phrase was explained by another in the thread. The only thing that brought enough attention for any comment was marcanās responses, and Linus just basically came in and said to stop making noise.
The words may be american but the mindset is the same for cops around the globe.
I think itās a big flaw of the mailing list system of the kernel development. Marcanās reaction led to everyone trying to āprotect the threadā from being āderailedā and ignore the actual comments that in themselves shouldāve been discussed properly.
Even leads to people here saying Marcan overreacted when I think on other social media platforms this wouldāve been its own conversation separate to the conduct of other users.
I say this purely speculatively since I havent ever held a longrunning group convo in a mailing list intentionally.
I think that Linusā concerns about posting on social media is completely valid, but I was pretty disappointed that he didnāt address Hellwig going full retard. Marcan dealt with this like a spoiled child in the end, but he was 100% right.
This should be worth a Linus rant in my honest opinion.
Hellwig specifically says āwhere this cancer is a cross-language codebaseā. Heās not wrong. I donāt know how you transition languages, but my god, if you want to lose maintainers, make it impossible to maintain because of language incompatibilties. A few people from a downstream project like Asahi or an almost defunct driver like Nouveau would be the least of your worries if you were Linus.
I disagree. Hellwig was not contributing with the discussion. The point is that Rust is being integrated into the kernel, whether Hellwig likes it or not. It passed the point of discussing if it should happen or not. Besides that, R4L is responsible for maintaining the Rust code even if something is broken from the C side of things.
Neither of those sides exist in a vacuum; itās great thereās a R4L team, but you still have to eliminate the possibility the problem exists at your end before you throw it in their lap and say ādeal with itā. And Iāll bet half the time it gets tossed back with āyour problemā and then the arguments ensue, not to mention the various discussions about how to make them talk to get rid of the bug. Itās not anywhere near as simple as the idea that there is a team for that.
Sure Hellwigās probably being an asshole here, but you can be an asshole and still be right. Linus did it for 20 years and built the most successful OS in history.
Yeah, I agree with you that, realistically speaking, Rust people would probably complain when C code brakes their code, but I still think that this was not what Hellwig was talking about.
In my opinion, he was just being unreasonable when he told people that he would be doing everything he can to prevent anything else thatās not C code from being merged into the kernel.
I mean, I understand his concerns of not wanting to deal with Rust code, but what he said is not contributing AT ALL to the discussion.
btw, Iām not the one downvoting your comments. I disagree with you but I think you are making some valid points.
Fair enough, I guess I would agree with you on the value it had to that discussion. Iāve just dealt with partial codebase transitions and itās a horror to fix anything.
And I couldnāt give a shit about downvotes, or Iād just dogpile along with the groupthink in every thread like the rest of the Lemmings. I appreciate the discussion.
Iām not sure why you think Asahi is a minor player in the linux community when theyāre responsible in the entirety for porting Linux to the Arm-based Mac M1+ series, or why you think Nouveau is defunct.
If a single percent of regular Linux users use either of those on a daily basis, Iāll eat a bug. And desktop Linux isnāt even a significant amount of Linux use in general. So why would the kernel developers give the slightest shit about either of them?
Nouveau is important because Nouveau is the default driver in Ubuntu, Fedora, OpenSUSE, Debian, and ever other distro.
Linux distributions canāt easily distribute the proprietary
nvidiadrivers or the slightly less proprietarynvidia-opendrivers so they depend on nouveau as the default nvidia driver. When you install a distro it usually has to use the nouveau drivers before downloading the proprietary blobs from Nvidia.Nouveau is the only reason anyone can use Linux on an Nvidia card long enough to install the other drivers.
Itās also actively maintained, receiving updates that get upstreamed almost daily.
Iām not sure what about those things says ādefunctā.
And the rust developments in Asahi for the M1+ series of CPUs donāt just benefit Mac but all the ARM CPUs as well.
gamingonlinux.com/ā¦/nova-a-rust-based-linux-driveā¦
Itās days of being the driver thatās used long enough to install the proprietary driver that actually works are numbered.
<img alt="" src="https://imgur.com/fbXhlkV">
This new driver is written in Rust, so it changes nothing about the debate
Man you better hope the kernel community gets its shit together then, cause Krummrich (the primary developer for nova and getting those changes upstreamed) is one of guys that got told their project was cancer by the āthin blue lineā maintainer (Hellwig) from the article.
.
āthe process worksā Is I think how he phrased it. š
Full message from Karol Herbst on LKML:
I was pondering with myself for a while if I should just make it official that Iām not really involved in the kernel community anymore, neither as a reviewer, nor as a maintainer.
Most of the time I simply excused myself with āif something urgent comes up, I can chime in and help outā. Lyude and Danilo are doing a wonderful job and Iāve put all my trust into them.
However, there is one thing I canāt stand and itās hurting me the most. Iām convinced, no, my core believe is, that inclusivity and respect, working with others as equals, no power plays involved, is how we should work together within the Free and Open Source community.
I can understand maintainers needing to learn, being concerned on technical points. Everybody deserves the time to understand and learn. It is my true belief that most people are capable of change eventually. I truly believe this community can change from within, however this doesnāt mean itās going to be a smooth process.
The moment I made up my mind about this was reading the following words written by a maintainer within the kernel community:
This isnāt okay. This isnāt creating an inclusive environment. This isnāt okay with the current political situation especially in the US. A maintainer speaking those words canāt be kept. No matter how important or critical or relevant they are. They need to be removed until they learn. Learn what those words mean for a lot of marginalized people. Learn about what horrors it evokes in their minds.
I canāt in good faith remain to be part of a project and its community where those words are tolerated. Those words are not technical, they are a political statement. Even if unintentionally, such words carry power, they carry meanings one needs to be aware of. They do cause an immense amount of harm.
I wish the best of luck for everybody to continue to try to work from within. You got my full support and I wonāt hold it against anybody trying to improve the community, itās a thankless job, itās a lot of work. People will continue to burn out.
I got burned out enough by myself caring about the bits I maintained, but eventually I had to realize my limits. The obligation I felt was eating me from inside. It stopped being fun at some point and I reached a point where I simply couldnāt continue the work I was so motivated doing as Iāve did in the early days.
Please respect my wishes and put this statement as is into the tree. Leaving anything out destroys its entire meaning.
Respectfully
Karol
Signed-off-by: Karol Herbst
For people who didnt understand the phrase like myself: en.wikipedia.org/wiki/Thin_blue_line?wprov=sfla1
Thanks for the context!
I hope the rust kernel devs join hands with redox or asterinas project. which ultimately means more options for users.
Yeah, Iād obviously want all these devs in Linux but BSD and Redox and many others will thoroughly appreciate their talents in the meantime.
Would also be interesting to see a Rust version of Genode
I think a sort of Linux compatibility layer could go a long way toward making Redox more viable. It may already have one, but that seems like a good place for an ex-Linux kernel dev to work.
The leadership response to this and the subsequent backlash is starting to remind me of the NixOS debacle from about a year ago.
That resulted in the project being split and like 30% of the community moving off and creating Lix.
I would be disappointed, but not surprised, if we see something similar in the Kernel sometime in the next year or twoā¦
Is there any write-up for the recent events around the kernel and Rust? Glancing over recent posts, it seems like new devs want to push Rust, but older maintainers donāt want to deal with it. Why do people love Rust so much? Is it just a loud minority or does it in fact offer substancial gains and safety over existing C code? Lqstly, can they simply fork the kernel and try their own thing? E.g. do a branch as a proof of concept and therefore convince them to migrate?
Forking the Linux kernel will effectively guarantee that no one will run their software. None, but the most niche distros would ship it. If the Rust people are forced to fork, their time may be better spent contributing to Redox.
Rust makes it very difficult (but not impossible) to write dangerous code, whereas C pretty much guarantees youāll write something dangerous (and therefore insecure or buggy) at some point, especially in larger codebases, like the Linux kernel. Arrogant devs will defend keeping Rust out of the kernel by saying things like āwrite better codeā, but if the people writing kernel code for 20 years are still writing dangerously flawed code, itās safe to say that at a certain point, we need a better tool. That tool is Rust.
Rust also has very high-quality libraries that produce nicer finished products. I learned Rust because of
clapandratatui, which make superior CLIs and TUIs to anything else. Seriously, go use a CLI or TUI that was made in Rust. Trybat, acatclone. Youāll get easy, great command-line completions, easy-to-read help output, optional, beautiful syntax-highlighting, theming, etc. Itās hard for me to go back to vanillacat.And I say all of that as someone that likes C. C is really fun, and itās a very powerful language, but it was not designed to be memory-safe. If it was, the people complaining about Rust would just complain about C too.
Thatās a simply amazing pun for a library name. I really enjoy the history of kind of silly naming within linux and programming generally.
From what I remember, itās much more difficult to accidentally leak memory in Rust. Combined with the drop-in compatibility with C and the somewhat more intuitive (imo) syntax, I can see its popularity as unsurprising.
I think the biggest thing is that there arenāt really that many reasons not to use Rust.
Leaking isnāt really the issue, though I suppose Rust helps with that as well. Its memory sales pitch is more about memory safety, which is not reading or writing the wrong parts of memory. Doing that can have all sorts of effects, where the best you can hope for is a crash, but it often results in arbitrary execution vulnerabilities. Memory _un_safety is pretty rare and most prominent in languages like C, C++ and Zig.
Rust also has more information contained in it, which means resulting programs can actually be faster than C, as the optimizer in the compiler is better informed.
Rust is already in the kernel and Torvalds wants more, faster. Heās being obstructed by C purists, who at this point are the people who should fork the kernel if they see anything but C as heresy.
Sorry to say it (and as much as i like C) but C is already on the path to inevitable obsolescence. Everyone is learning Rust now and fewer people are learning C. Maybe not soon, but definitely eventually. Linux can join C on this path to obsolescence or it can pivot to a language that still has a clear future.
Rust will go obsolete a some point too when the next next generation of languages come out. And software projects using Rust will have to switch languages again to stay relevant.
Donāt forget that languages like COBOL was once state of the art but was replaced byā¦ C.
Thatās just the computer circle of life.