Comment by eviks

> Much harm has arisen out of the superstitious fear of 100% CPU use. Why wouldn't you want a compute bound task to use all available compute? It'll finish faster that way.

Because it hurts the speed/responsiveness of stuff you actually care about. It also has other negative side effects like fan noise and temperature, which with bad insulation in MacBook it can even physically burn. Pretty obvious stuff if you don't discard issues as superstitions

> It'll finish faster that way.

The usefulness of which might be none: some background maintenance process finishes in 5 seconds that I don't notice vs in 1 seconds while turning the fans on or making my app slower

> We keep the system responsive with priorities and interactivity-aware thresholds,

Only in your fantasy, in reality you fail at that, so "superstitions" arise

> It's hard to blame Apple for locking down the OS core like this.

Of course, if you ignore real issues with bloat, and only notice the mistakes, but that's a self-inflicted perspective

> by disabling load-bearing services

The article mentions that there is not even basic information on what services do, it's similar in Windows, so maybe the proper way out is teach people and also debloat the OS proactively to give them less of an incentive to do it themselves?