I’m not sure if these are real questions or rhetorical. Just in case they are real…
Sounds like a matter of permissions. What do you see on your system? Here’s what I see:
$ ls -ld /Applications /Applications/Utilities
drwxrwxr-x+ 92 root admin 3128 Jun 11 12:43 /Applications/
drwxr-xr-x+ 28 root admin 952 Jun 9 09:47 /Applications/Utilities/
Both folders are owned by root:admin, but note the permissions. /Applications
is group-writable, so anyone in the admin group (that is any, account you configured to be an administrator) can copy files there. /Applications/Utilities
is not, so everybody must authenticate before copying files there.
I don’t know why Apple did that. Probably to make it easier for administrators to install software.
If you don’t normally log in to an admin account, which is a very good practice, then it doesn’t matter - you’ll be asked for an admin user name and password before copying files to either location.
Because the system doesn’t know if you deliberately installed it or if it got installed through some other means (e.g. malware). By making you confirm your intent, you have the chance to abort launching something that you didn’t install.
In the Classic MacOS world, some of the worst instability problems were the result of people installing “haxies”, including APE and SIMBL. Either because the extension was buggy, or because it interacted badly with other haxies that were all installed and running together.
Even if you know exactly what all the risks are, most people installing these did not (and still don’t). They’ll just read random forum posts by people advocating various add-ons and install stuff they don’t understand. And when the system becomes flaky as a result, they blame Apple, who has to spend a lot of tech support money to figure out that the user’s problem was self-inflicted.
Yeah, I’d also like to customize these things. But Apple has always been this way. They don’t want users changing the look and feel of the system, and they definitely go overboard with things like this. But this is nothing new.
Using new system permissions to block access might be recent, but as far back a System 7, Apple was known for shipping system updates that would revert any such changes, forcing you to redo it all after every update.
I’m not sure I know what you’re talking about. You can still download and install apps from any source. Apps need to be signed and notarized in order to launch the first time with a simple double-click, but that’s hardly a heavy pressure thing.
The App Store is so popular is because it is easier to distribute software that way than through other means. But there are plenty of publishers who distribute their software in other ways as well.
And how many non-experts will say “yes” to that question and then go crying to Apple’s tech support when they make a complete mess of their computer? Probably everybody.
This is as much an issue of reducing support costs as it is anything else.