HN has a rule about titles to avoid derailed threads like this.
3,314 karma · joined May 8, 2024
HN has a rule about titles to avoid derailed threads like this.
AI cannot squeeze blood from a stone. We still have outstanding issues (eg. PSCI support) that AI hasn't reverse-engineered. Is that "pretty soon" supported, too? What about the Secure Enclave? Do you think there's an ice cube's chance in hell that Linux ever supports it?
Unless you're willing to prove that AI can do this stuff, kindly refrain from making ridiculous predictions because "muh AI" will allegedly fix it. It won't. There are undocumented interfaces that AI will never fully reverse-engineer, that's just how Apple designed their SOC.
And yet they have a total of zero upstreamed PRs, and haven't fixed enormous and glaring issues like PSCI control either.
It's almost as if the parent is correct, and Apple's ARM architecture isn't standardized enough for ordinary models to blindly reverse-engineer without documentation. If tokens were the only constraint on supporting Apple Silicon, we'd have reversed the entire SOC device tree years ago. Alas...
If you think that laptops deserve to become e-waste when the OEM says so, then your opinion can be safely discarded.
Apple eventually stops OEM support for Macs, which means that support via an alternative operating system is a foremost imperative.
I'm sorry that you're absorbed in your fantasy, but it's not my job to accommodate it.
How, exactly? AFAIK, Asahi officially supports just as many Macs as Omarchy does. The vast majority of Apple Silicon support in Omarchy comes from upstream Linux changes merged by Asahi, not any of the Omarchy devs.
The only feature I'm aware of Omarchy adding is the fingerprint reader driver, which is in such a poor state that it could never be merged upstream. Which, if that's the standard of quality Omarchy is holding themselves to, they're the ones getting left in the dust.
Methinks the lady doth protest too much.
You're part of a minority.
> What other things outside of containers or iPad apps?
Linux with fully native Vulkan drivers, for one.
You're downstream of all of those kernel and Mesa changes on Gravity.
I have no particular love for Asahi, but they've made 10x more progress than the vibe coded alternatives.
Bully on me for expecting narcissists to grow a spine.
It may shock you to hear that coding was never the bottleneck for emulation or reverse-engineering.
Perhaps the 30+ years of non-LLM generated Linux support for UEFI/ACPI and ARM device tree chips has something to do with it.
> It is quite remarkable how far along support has come
Is it? All I'm seeing from that page is that they forked Asahi's M1-M4 work, and then failed to bring up M5 and M6. What's remarkable here?
They run other things, too. There's no valid technical reason it can't or shouldn't, and Apple deserves the scrutiny if they won't bring macOS up to parity with Linux. Modern macOS is legitimately terrible, and ~100% to blame for why Macs are shunned for HPC, on-prem and other professional applications.
The modern Lenovo keyboards aren't perfect, but they're comfortable for desktop-esque use. Plus, I prefer the arrow cluster with pgup/pgdn nearby so I don't have to reach for the function key every time. It's also nice to be able to buy a replacement on Ebay for $20, too.
And more importantly, documenting Mac hardware takes time. Components like the speaker on a Macbook can be permanently damaged if you don't write the drivers in a specific way. Other features like the Secure Enclave, power management, and TouchID might be unsupportable depending on how Apple designed it.
Asahi's stance isn't particularly crazy, and it probably aligns with how Linus feels about upstreaming code that nobody understands.
For the brief period where Apple refused to sell you non-Butterfly keyboards, it was one of the best ways to use macOS.
ActivityPub, AT Protocol, Nostr, to name a few.