The thread about it generally reaches 40+ pages before Apple erases it only for it to come back. Apple has known about it for half a decade. I can pinpoint the OS release when they broke it. Sure, it doesn't seem to affect everybody, but the people it does affect have no recourse.
With MacOS, as long as everything works, everything works. But, when it doesn't, you cannot do a damn thing about it.
Linux very, very rarely leaves that kind of catastrophic bug for 5+ years.
I tracked it to a single OS update because it was one of the last iterations that still had removable SSDs. I could swap the drives and the USB failure moved with the OS.
It's almost certainly an overly zealous macOS USB HID driver. macOS will do very strange things if the HID descriptor and the USB report don't correspond exactly and it will do those weird things silently. People have had to work around strange macOS HID handling for quite a while now.
My past two laptops, ASUS and Lenovo, lasted days with modern standby. Not as great as Apple but good enough.
Therefore, if you ever have a problem with Linux on your PC, it is your fault for expecting Linux to work on your non-compatible PC, and you cannot blame the difficulty of fixing the problem on Linux.
https://immi.homeaffairs.gov.au/what-we-do/whm-program/lates...
If nothing would lead a reasonable person to believe it is supported then your default assumption should be that is likely not.
If the functionality that one expects to work works as expected on supported hardware but not on yours then Linux isn't broken your hardware is.
If it doesn't work on previously supported or otherwise well supported hardware its a bug in the software.
It's weird that compatibly is discussed as if for the next 20 years one shall be forced to use a succession of randomly chosen machines and compatibility will ever be a crapshoot.
Often people will initially try Linux on random machines but official Linux machines are out there and those who have decided that Linux meets their needs can easily find well supported hardware.
Whenever I buy a new piece of hardware of any sort I end up reading lots of spec sheets, reviews, and articles and comparing choices according to a whole range of desirable features. Making Linux support one of them hardly makes it any more complicated.
If nothing else search for product category + Linux then find a list of recommendations and then google choices that look good looking for unbiased critique focusing especially on people claiming systemic flaws in design that effect all units.
Actually, I had fewer compatibility problems with Linux than I had with Windows, using absolutely non-esoteric hardware, like Thinkpad laptops, Asus motherboards, etc. Hell, sometimes it was easier to set up a printer under Linux than under Windows (which, frankly, is more often the other way around).
But usually Linux, and to a smaller extent, Windows, allows you to cobble your own solution if a solid predefined solution is not available.
MacOS is much more often a "my way or highway" kind of environment. Some enjoy it; I don't.
And or pay to know the actual truth about when the last time you used an up-to-date distro was.
My NixOS laptop is by far the most, stable consistent, unchanging device in my entire life. Speaking of which, shout-out Google for breaking LDAC on their most recent Pixel 9 updates.
This is absolutely insane.
I'm sure Apple will claim to have a very good reason for this, but the concept of controlling volume on audio devices has existed since the dawn of computer audio. All other operating systems do this as expected.
This is my main issue with using Apple devices. You either accept their vision of how to use the device you paid for, or consider yourself lucky that a 3rd-party solution exists (and that Apple has allowed to exist), which you also usually need to pay for. Insanity.
[1]: https://old.reddit.com/r/macmini/comments/lgfjax/is_it_possi...
It's why I only use hardware with fixed dongles (Jabra, Logitech, etc).
Didn't Apple kill deep sleep/hibernation when transitioning to ARM ?
It was touted as "Always On Processor" to mimic the iOS and iPadOS management of CPU and never shut it down.
> One of the lesser known facts about the Apple M1 chip is it has an always-on processor. This means that even when your Mac goes to sleep, it isn't really completely asleep. Macs with Intel chips have had a feature called Power Nap for a while now. M1 Macs don't need that feature because it's built-in and automatically running at all times.
https://www.xda-developers.com/first-10-things-to-do-m1-mac/...