um isn't there only one comment that matches what you're describing? i actually thought it was pretty neat how that discussion started out in the vein of a twitter thread, with one person misinterpreting another person's tweet and moralizing about it, but then you have that super long comment from alyssa 6 hours later that says "i think you're both right" and goes way into depth about how things are the way they are
on twitter there wouldn't have been the space for that comment and it would've been overrun by a bunch of people making quick moral judgements about a tweet they deliberately misinterpreted
"I just realized that one of the things that bugs me is people equating stereotypical Linux problems on Asahi with other platforms, because it's not the same, because we actually care.
Suspend not working, audio not working, display tearing issues, power management being bad... all those things are Linux on $random_platform support memes. And they're memes because they never get fixed, because nobody cares."
It's evident if one looks at endless bug reports, mailing list discussions. Many users and maintainers care. But even though they do, the bugs are not trivial.
Many strange bugs are a consequence of subpar software architecture. One example that comes in mind is a bug about the xfce(?) lockscreen and laptop lid closing, that only activates when the lid opens. So for a time the desktop is visible. (There's also one bug where the password input field is invisible in some cases, etc.)
It seems security and UX critical functionality is broken.
But the truth of the matter is that it's also broken on many Windows setups too, just in other ways. Eg. complete freeze on restore.
Or look at the GitHub issues for WSL, there are a lot of strange bugs, like DNS stops working and only reboot solves it. And those Microsoft engineers care even less than some open source maintainers. (For example the TypeScript maintainers are very responsive, even though that repo also has a lot of bug reports.)
https://codeyarns.com/tech/2017-01-18-the-two-clipboards-in-...
I spend my days in aix and my evenings in windows. Every time I use Linux though, I get frustrated at seemingly completely unpredictable behaviour of clipboard! Now I at least have a basic understanding of the model - thx!
(There is actually more than two)
Hector's point is also that the ability to fix the bugs is diffuse: to fix a problem with the SSD you ultimately need to get the SSD maker to care. To fix a bug with the sound, you need to get the sound chipset maker to care. And actually to get a broadly good user-experience such that it works good not just on your system but every possible system, you need to get an awful lot of people to care.
As ever, one of the plusses of the Apple platform is the absolutely fixed set of hardware it needs to target. There is only one wireless chipset that Asahi needs to get working, for example. There is only one sound chipset they need to get working. When it's working, it's working for everyone, and if there's bugs they're bugs that affect everyone and aren't a result of some obscure combination of drivers interacting in unexpected ways.
Also, Apple actually internalized a lot of control in ways that really piss people off when they want to upgrade hardware, but it also means the SOC has a lot of power to just do things right in the first place since it's all software-driven anyway. You don't have to worry about the NVMe controller doing something weird because... the NVMe controller lives on the SOC (might even be fully software-defined?) and just talks to some flash chips sitting on a card. It's completely different from how the rest of the market does it, and it's undoubtedly more work to get it going, but it also (paradoxically) means they don't have to worry as much about hardware quirks, because there's less hardware in the middle to begin with.
It's undoubtedly a reason they've been able to make such great progress - not that the dev team isn't extremely extremely talented anyway. But they don't have to solve the general Linux problem of getting 10 billion possible permutations of hardware to behave together. They just have to solve one platform with one set of peripherals.
But what I find very frustrating is that many software projects - especially open source ones - don't really think about the end-to-end user experience and don't have "interfaces" to help manage the UX, as in signal that the device is not respecting some standard/protocol/API/whatever. At best there's some obscure error message. Assertion failed. Blahblah.
I mean ... I know there were latops with Ubuntu stickers, but it's just not a big thing - as far as I know. Sometimes niche manufacturers with some newsworthy feature (FOSS firmware, drivers, etc) get into the news, but that's why it's news, because there's just no run-of-the-mill boring supplier...
This linked post is pretty clear example of that - after decades of hundreds of people making sure that hundreds of configurations worked very well on Linux, he's now all smug because they're working on a single Apple configuration.
The social interactions he ends up having are of his own making as well.
And that's all even if we ignore Android and ChromeOS devices exist.
It doesn't make Hectors contribution any less important for all of the Apple fans, but putting down other Linux developers like this is disgusting.
I love those "I had issues so everyone else must have had them too" takes. I can give some anecdata too: the last integration issue I had on machines I've been running GNU/Linux on was a non-working SoundBlaster Audigy card somewhere around 2006 - and I've been mostly using laptops afterwards, some of them being from vendors that didn't provide any GNU/Linux support at all.
(that sound card eventually gained support in ALSA, by the way)
But I am not sure it works well. Hibernation never worked. Was performance, sound optimal ? Battery life ? I love that they are working on thing like that.
For laptops however, hardware support is still terrible or nonexistent. If you have a modern wifi 6/6E chipset, a fingerprint sensor, or a webcam that uses the chipset ISP, there's a very good chance it's unusable. Battery life is still a decade behind state of the art.
Nowhere in the linked post does he talk negatively about those efforts, more about hardware manufacturers not doing their job. But he's objectively right about the average Linux experience on a random laptop. I have never owned a hardware configuration where everything worked with Linux except for the Steam Deck. My best experience was on a Thinkpad from 2016 and on that one I still had to adapt and compile my own wifi driver.
Don't know the guy, but from my experience people who "vehemently contest" the opinions and viewpoints of project leaders can come off arrogant and know-it-all from the POV of the people who are actively working on the project and bootstrapped it from zero to success.
It's one of those "clash of the titans" scenario.
I mean it's to be expected: a popular project gets a lot of praise but also a minority of vocal critiques.
How single project leaders react, unless they are obviously abusive and/or violent on average/randomly, it's not really that important IMO.
> The social interactions he ends up having are of his own making as well.
That doesn't make him wrong, this topic in particular is a real pain point: manufacturers don't care about Linux users at all, it's their fault if Linux is mostly a less smooth than it could and should be experience.
> we actually care … they never get fixed, because nobody cares
He's pretty explicit. He thinks he and his care more than other distributions.
I'm sure his observations have nothing to do with only supporting two related SoCs vs thousands of disparate chipsets, and the ability to repro from there.
It's a terrible comment.
Plenty of hardware gets attention for exactly the same reason M1/M2 do. It's nothing to do with care, everything to do with access.