The “bug” here is system activity I’m not deliberately invoking.
Are those programs written well, or are they using so many cycles because they’re inefficient and slow? And when did I ever opt in to this? Spotlight has slowly gotten more and more horrible over time. Half the time I use it to invoke system preferences it can’t find it. Or it can’t find the applications folder. If Spotlight is this terrible, why is the hard disk indexer so busy? Is it any better engineered than spotlight? I doubt it. Likewise, I don’t want photoanalysisd looking at my photos. I don’t use that “photos by person” feature. Why does it use hour upon hour of cpu time to make this feature available - just in case I use it later I guess? Get lost.
I really wish Apple stopped adding random crappy features to macOS that I don’t use - but which burn cpu cycles. Instead, fix your shit. Indexing is fine if you make spotlight actually be good again. Photo analysis is useful if I decide it’s useful and turn it on. And maybe if Xcode and SwiftUI weren’t such a buggy, crash ridden, undocumented mess, then maybe, maybe, I’d trust you more to run random background processes.
As it stands, I don’t trust Apple - particularly their application teams - to be good custodians of my cpu.
https://forums.dolphin-emu.org/Thread-wiimote-pairing-macos-...
The bluetooth stack in Windows and Linux does.
Apple's official position is that my wiimotes are the problem and I should buy an Apple supported bluetooth game controller.
Presumably one of these four controllers:
System activity can certainly cause problems like paging out all the file cache pages you wanted to use when you get back to the machine. It doesn't have to though.
