Passing the torch on Asahi Linux - Asahi Linux
Passing the torch on Asahi Linux - Asahi Linux
asahilinux.org
Passing the torch on Asahi Linux - Asahi Linux
22 comments
-
-
Have it on my M1 MacBook Air and the experience is solid. Sad to see one of the original crew gone. Reading his blog makes it sound like he’s burned out again - it was sad to read both for him and also sad because his perspective of the user base is also oddly skewed. He was surprised users wanted better battery life? That’s one of major selling point of the hardware platform. Surprised users wanted external display support? “Can’t you just be happy with what I gave you?” Bit of a strange take that makes me think he probably needs a long break away from something that’s become both too personal and toxic. I’m saying this because I’ve been there and can empathize.
But hey - grateful this project exists. It means Apple Silicon Macs have a much more open future.
-
I would have figured the whole point of the project is getting to feature parity, right? It makes it a harder sell if you lose a bunch of them when migrating to Linux.
-
That’s my feeling too.
And I’ll keep surporting them financially whether they get there or not.
But the whole “users act entitled by [insert basic feature]” leads me to believe other issues are clouding Martin’s judgement.
It’s a really wonderful project and it’s great to see the rest of the team deciding to use this event to build an even more resilient organization.
-
-
his perspective of the user base is also oddly skewed. He was surprised users wanted better battery life? ... Surprised users wanted external display support?
I think this misconstrues his point: he was talking about a subset of users ("entitled users"), not calling all the users entitled.
To me, it seemed less that he was surprised users wanted certain features, more that he was burned out by the feature requests that spent time expressing personal grievances, making demands, or getting mad about the project's pace. I understand that might come off as him being overly-sensitive, but I absolutely see why a constant cascade of FRs written like demands instead of no-BS questions would wear down on someone, especially while they're simultaneously trying to deal with upstreaming.
he needs a long break away from something that's become both too personal and toxic
I totally agree here though, I just hope that this whole fiasco isn't written off as the result of some vague burn-out. There really does need to be some change in kernel maintainer authority structure and the culture. That can only really happen if someone respected (e.g. Linus) makes some moves to encourage more cooperation/openness from certain C maintainers, and helps put in place better guidelines for how Rust contributions should be handled. It's simply too disorganized right now, and that makes it too easy for individuals with power to let their egos get in the way of good progress.
-
I have to respectfully disagree about misconstruing his point. From his blog post:
But then also came the entitled users. This time, it wasn’t about stealing games, it was about features. “When is Thunderbolt coming?” “Asahi is useless to me until I can use monitors over USB-C” “The battery life sucks compared to macOS” (nobody ever complained when compared to x86 laptops…)
This points to someone who did a thing because it spoke to them on a “shiny, complex, technical problem” level but without any deep understanding about what those who might use it understand the end goals to be. If I wanted Linux on a laptop with x86 battery life, well that’s mostly a solved problem and that platform has ample support for external displays and connectivity.
So while I truly empathize with Martin feeling “burned out from dealing with entitled users” - having managed a very popular technical open source projects in the past - it’s still indicative of an impedance mismatch between his goals and what others might reasonably infer are the end goals for a project like this.
Again, it sucks because it doesn’t have to be this way. We could all act less entitled. But I also don’t think Martin is all victim here - at the very least he’s also victim of his own expectations. As we all often are - myself first and foremost.
I remember getting on a call with a particularly aggrieved open source contributor who claimed, in no uncertain terms, that it was our duty to take any and all PRs thrown at the project, no matter how poor they were, or how problematic they were to maintain. Again, I think most of us would agree that’s unreasonable, but there it was, stated without irony, and to my face.
It would start to eat at anyone. So again, I’m not faulting Martin here, I’m just expressing some surprise at his own surprise for what seem like perfectly reasonable requests and ones the team did very well to address directly and clearly on Asahi’s main page.
-
-
-
As a solid outsider, this whole Rust thing seems like it keeps simmering under the surface in a way that could one day boil over and seriously damage the entire Linux project.
I don’t have a machine capable of running Asahi today, but I also don’t feel like I need it now. Reading this and reading marcan’s resignation makes me feel like I should find some way to chip in to Asahi now so that whenever Apple eventually stops supporting my hardware, Asahi will hopefully still be there and ready to keep the hardware going. I figure I probably have about 6 years of Apple support, but I’m also suspecting Apple might support the ARM hardware longer than they ever did Intel or PowerPC, so I might have even more time.
-
... Asahi will hopefully still be there and ready to keep the hardware going. I figure I probably have about 6 years of Apple support ...
i used to use & contribute to linux/foss projects for ppc architectured macs and it took years for them to be fully supported at the same level that intel architectured users enjoyed; chipping in now is the only way that something like asahi is ready to take over once apple inevitably leaves you out in the cold like it did its ppc (and soon intel) users.
they have excellent hardware and it would be a shame to throw it away or allow it to collect dust when you can't get 100% utility out of it simply because your options aren't developed enough at the time you need them.
-
You are just being silly, there is no way its going to "seriously damage the entire Linux project". There is nothing too technical about the whole R4L drama (esp. the recent one), its mostly political opposition to Rust from some C folks. We have seen this before in Linux (Wayland/X11, systemd/sysv, etc.).
-
The problem is that those issues have, and continue to, cause damage to the Linux project. Good maintainers have been hounded out, or simply given up, and bad blood exists where it absolutely shouldn't. You're right that much of it is political, although that usually stems from deep technical differences backed up by corporate encouragement. Political turmoil can be as damaging, if not moreso, than technical differences. At least technical differences can usually be resolved technically, politics is infinitely more nuanced.
From Marcan's description, the way certain people treated him was absolutely unacceptable, although I've no doubt they'd describe things very differently. I hope the whole kernel team, maintainers and contributers, can find a way to work through these differences and work more harmoniously before more members end up burnt out, frustrated and bitter.
-
-
As a solid outsider, this whole Rust thing seems like it keeps simmering under the surface in a way that could one day boil over and seriously damage the entire Linux project.
I feel like it might cause a hard fork
-
Linux is what keeps my Macs alive 🤭
But this is good thinking
Think like jqubed
Donate in your future
See far
Peace
-
I agree. For everyone’s sake they should rip Rust out and put all that effort into RedoxOS. There is way too much misalignment for this to be constructive.
-
-
Our king Sir Torvalds has spoken. And hence let there be rust in the kernel
-
Calm down, he isn't the sole regent of the kernel, you know.
-
22 comments
I wish them luck and hope they can find better ways to work with the existing maintainers.