Answering as a linked topic, because I expect this to generate a lot of comments…
Continuing the discussion from How to Avoid Sequoia’s Repetitive Screen Recording Permissions Prompts:
When was that?
Since day-one, any option that Apple didn’t provide in a control panel or preference panel somewhere always required some degree of hackery. Typically by installing third-party software that would hook itself into some part of the OS (e.g. INIT, system extensions, kernel drivers, background apps, etc.)
And the developer of those “haxie” packages typically needed to figure out the knowledge they needed the hard way - by using undocumented data structures and functions, hoping that future versions of the system software won’t break them.
Or by editing system resources (e.g. icons, fonts, images) using developer tools like ResEdit.
It might have been “easy” for ordinary users to buy or download one of these haxies, but it was far from easy for their developers.
This is compared to the typical Unix system, where anyone with the skills to be a system administrator (generally) had all the tools and knowledge to customize everything, thanks to a combination of open source code, software designed for massive customization (often with lots of cryptic configuration files) and really good documentation.
Mostly (I assume) due lots of fundamental development being done by the hacker communities at Berkeley and MIT (in addition to AT&T’s research group, which was also pretty hacker-ish).