- cross-posted to:
- phoronix@lemmy.world
- cross-posted to:
- phoronix@lemmy.world
Following arguments on the Linux kernel mailing list the past few days over some Linux kernel maintainers being against the notion of Rust code in the mainline Linux kernel and trying to avoid it and very passionate views over the Linux kernel development process, Asahi Linux lead developer Hector Martin has removed himself from being an upstream maintainer of the ARM Apple code.
You must log in or register to comment.
Damn, Linus really went out of his way to say:
How about you accept the fact that maybe the problem is you. You think you know better. But the current process works. It has problems, but problems are a fact of life. There is no perfect. However, I will say that the social media brigading just makes me not want to have anything at all to do with your approach. Because if we have issues in the kernel development model, then social media sure as hell isn’t the solution. The same way it sure as hell wasn’t the solution to politics. Technical patches and discussions matter. Social media brigading - no than\k you.
…but still fails to answer the question of “should we continue implementing kernel things in rust”.
That’s a shame irrespective of the drama. Asahi is surprisingly good. Installation is (relatively) straightforward.
I’ve got it on my primary laptop. I don’t use it frequently because battery life is poor compared to MacOS and I can’t use an external display but it’s an impressive achievement and I’m sure it will only get better. I haven’t used fedora in 20 years but it’s slick and easy and most of it just works. It looks just like my Linux workstation desktop.
It’s really a bummer seeing how much childish drama is in the Linux dev community.
I am not nearly a good enough dev to contribute to the Linux kernel, but I am working my way towards that point currently at night after my kids are in bed. Be the change and what not.
That’s a good way to take a bad situation and make it better. Good luck! Maybe I’ll join you one day.
The anti Rust bullshit is gonna kill Linux’s growth.
it seemed like the innocent(ish) holy wars of the past like emacs vs vi; but it’s taken on a whole new destructive trajectory of its own and the old guard would rather see Linux ossify into irrelevancy rather than letting the next generation take over.
it reminds me of an old quote from a general to the effect of: if 5 americans survive a nuclear war and 4 russian survive; then we’ve won and it was worth it.
either that or it’s like the technological equivalent of the the democratic leadership w disaffected democratic voters leading to defeat in this last election or an elderly driver whose grown children are trying to take away their keys before things get worse; all are refusing to acknowledge the writing on the wall because they think they still got it, but they don’t.
Unless those old farts die first
This news along with the news of WiFi driver maintainer stepping down, feels like there won’t be any new blood in Linux kernel development except for corporate funded developers.
It seems a lot of new developers want to do some things differently; old guard devs can either make some compromises, or accept that fewer new devs will want to be part of upstream.
I’m not too new to linux, but also not too veteran, has it always has this shit drama? There is always some sort of fucking child throwing a tantrum about some shit. Has it always been the case? It’s really getting annoying.
It has always been like this.
Man, this is so unfortunate :/
There is always some sort of fucking child throwing a tantrum about some shit. Has it always been the case?
Petty much. The big difference this time is that there’s a common enemy (Rust) instead of relatively isolated petty crap.
Unsurprising. You don’t have to follow Hector Martin on social media for very long to learn that he’s a petulant, indignant, self-righteous drama queen.
I’m not going to deny that he can act aggressively, but his point is still valid. The anti-Rust sentiments of some maintainers has slowed down the upstreaming of Rust into the kernel. It doesn’t make sense to waste people’s time by letting R4L limp along in its current state.
R4L either needs to be given the go-ahead to get things upstreamed, to the dismay of some Linux maintainers who don’t like Rust, or R4L should be killed and removed from the kernel so we can stop wasting people’s time.
Personally, I think killing R4L would be a major mistake. Android’s Linux fork with Rust support has been a major success for Google and significantly cut down on vulnerabilities. And the drivers for Apple’s M chips has been surprisingly robust given how new they are and for being reverse engineered.
Sounds a lot like Linus Torvalds back in the day, just saying…
Some similarities but the main difference in my eyes is that Linus doesn’t have a permanent victim complex.
Well shit
I wish rust ppl would listen to the maintainers of the 30+ year old c project.
They have decades of experience maintaining and patching contributions made by people who are no longer active and the small request that those contributions be in the language of the project isn’t something to fight against.
It’s really a bummer when skilled developers fall back on stuff like “if shaming on social media doesn’t work, what am I supposed to do?”
the small request that those contributions be in the language of the project isn’t something to fight against.
When the contributions not in C are explicitly approved by the project owner, it seems that the 30+ year maintainers shouldn’t try to blockade any progress from actually happening. Working multi-language projects isn’t that much of a nightmare, if code governance and boundaries are well-defined and enforced.
Definitely a case of “everyone sucks here”. The maintainer being a dick and sabotaging R4L without technical justification and Hector putting it on blast.
Dunno man, when what the dev of 30+ years said was more or less “fuck off”, it seems that advice was in fact heeded
The system works
What sort of advise are they giving? I’m out of the loop
https://lore.kernel.org/lkml/20250108122825.136021-1-abdiel.janulgue@gmail.com/
Here’s the whole thread if you wanna read for yourself.
My take away is that rust people are generally fine and try to abide by the norms of the kernel development process but Martin acts like a jerk and it would be okay if he didn’t come back.
See the comment far, far down in the thread implying that he’s somehow a more serious commenter or developer because he’s funded by donations as opposed to a company.
The holy and sage advice of the dino developers is to not do Rust. You know, not do a thing that Saint Linus himself authorized. Except Saint Linus is apparently not willing to walk the walk in this particular case.
We’re overdue for a Linux fork anyway.
Maybe im wrong but with ARM being the new cpu architecture, rust being new, wayland coming into maturity, etc, it appears as though there might end up being a more x86/x11/C focused legacy kernel and a forked ARM/Wayland/Rust focused new generation one.
Which honestly im fine with. And kinda makes sense. Especially if we get into an era where stuff like x86 starts to get phased out entirely. Which i think we will in the next decade or so. Remains to be seen if thatll happen but i think theres a decent chance at this point.
Maybe im wrong
Correct.
Wayland
Is there anything in the kernel that makes it compatible with X11 or Wayland over the other? I know that there’s a graphic driver discussion in the background, but still.
Im not a dev so idk about that tbh. But i know atleast that programs have issues with it. Its pretty good these days but some stuff still has to use Xwayland as a compatibility layer.
The kernel is unrelated to the choice of display manager.
