Comment by porphyra
8 hours ago
The whole reason why people are trying to replace them is because they have stubbornly refused to use AI, which has directly impeded progress in getting M3/M4/M5/M6 working. It's fine of course for them to continue pursuing their hobby of doing everything manually, and honestly it is insanely impressive.
But most people just want stuff to work, so it's odd to complain about it when others do manage to get it to work using AI to build on top of their prior permissively-licensed work.
Wanting stuff to work is a valid reason to not use AI for more sophisticated development projects. Having a computer that kernel panics once every three days is useless to me, even if it works for you.
A kernel panic is the least of your worries with this hardware. Asahi had to introduce a custom daemon to avoid frying speakers. Apple doesn't need to care about making the hardware interfaces safe if they control the entire stack, so they don't, and expose dangerous capabilities to the OS.
There was a fun period of time where Boot Camp still existed, but Windows could fry the speakers because it didn't have any of macOS's thermal protection. I think this was after the 2016 redesigns, as I had a mid-2015 with no such issue.
Linux kernel itself is AI development friendly.
Some of us think that is a mistake.
3 replies →
That's not what they meant. It's AI friendly, not slop-friendly.
There's a reason no Omarchy patch of any kind has made it to the kernel list yet. I did personally look into some of their code and it is certified, hacked-togeter slop.
4 replies →