Isn't the entire premise of the system being discussed here is that developers are forced to use it? So then why not just force developers to use the first thing you described?
It would break existing applications. Apple is hardly like Microsoft when it comes to back-compat, but they know enough to not break everything overnight: they can’t damage macOS’ credibility as a “real” desktop OS too much.
The main reason is that it’s a simple fact-of-life that software needs to be able to interact with other software, with or without permission (e.g. part of my day-job involves LoB integrations between software vendors that either went-out-of-business, despise each other, or live on vendor lock-in and offer no export/import functionality (looking at you, Progress, Clarion, and others…) - my work would be very difficult - but not impossible I’ll admit - if it ran on
(Fwiw, I always follow PLP when creating daemons, their service-principals, and FS ACLs, I’m always amazed at how everyone else (esp. multimillion-dollar ISVs) runs their MSSQL Express instances under SYSTEM, with ‘sa’ enabled, where every install uses the exact same single hardcoded password; often with LAN router port-forwarding on 1433 for “remote support” (don’t forget TeamViewer or Splashtop too). Sorry I’m ranting but the amount of security-incompetence still rampant in the LoB software industry today is flabbergasting)
It would break existing applications. Apple is hardly like Microsoft when it comes to back-compat, but they know enough to not break everything overnight: they can’t damage macOS’ credibility as a “real” desktop OS too much.
The main reason is that it’s a simple fact-of-life that software needs to be able to interact with other software, with or without permission (e.g. part of my day-job involves LoB integrations between software vendors that either went-out-of-business, despise each other, or live on vendor lock-in and offer no export/import functionality (looking at you, Progress, Clarion, and others…) - my work would be very difficult - but not impossible I’ll admit - if it ran on
(Fwiw, I always follow PLP when creating daemons, their service-principals, and FS ACLs, I’m always amazed at how everyone else (esp. multimillion-dollar ISVs) runs their MSSQL Express instances under SYSTEM, with ‘sa’ enabled, where every install uses the exact same single hardcoded password; often with LAN router port-forwarding on 1433 for “remote support” (don’t forget TeamViewer or Splashtop too). Sorry I’m ranting but the amount of security-incompetence still rampant in the LoB software industry today is flabbergasting)