The problem with this is that you'll always have exceptions, and eventually you have enough of them that users become accustomed to blindly hitting "Accept" to any permission dialogs.

If you keep a child out of the kitchen because the stove is hot, you'll protect them burning themselves, but you'll also prevent them from learning how to cook.

If people don't get the opportunity to fuck up, you arrest their development. Stupid software users then becomes a self-fulfilling prophesy. Users will become dumber than they ever were before, and therefore more and more reliant on software developers to do/make everything for them. In my cynical moments, I suspect this is all intentional... Imagine if the fast food industry were throwing their weight around to promote the idea that children should be kept out of kitchens.

I think your reasoning here is flawed. People do not all need to develop skills in all aspects of life. By keeping someone from experiencing physical violence you may prevent them from learning how to defend themselves, but by many this would be considered a fair trade.

I believe the same is the case with limited control over technology. Most users do not care to learn, and would opt to actively avoid the opportunity to learn if the associated danger was removed for them.

In my opinion the best option is to remain in the current state by default and have a more obscure 'power user' option that could be enabled within the OS itself.

Serious question: why should anybody have to learn how a computer works?

I mean, I do it for a living and I'm glad I know.

But I don't really know how bridges, or electric guitars, or cars, or genetic engineering, or oil paintings work.

It's awfully gatekeeper-y to insist that computers should be these totally wide-open, unsafe spaces.

I mean it's almost exactly like saying people should know how to rebuild an engine if they want to drive a car.

It's certainly good to know how to rebuild an engine, but surely many people should be able to use cars without knowing that...

I like your car engine analogy; car's have the same level of widespread use as computers, yet I would wager a large percentage of people would struggle to perform much in term of car maintenance. Anecdotally, I know a multitude of people who have no idea how their car engine works, so much so they would not know how to check the oil level.

As a further point, drivers are (with edge case exceptions) not kept away or locked down from performing any work on their vehicle, yet in most cases they would still prefer to pass the responsibility on to a trusted professional.

It's certainly good to know how a car works, or a computer works.

Recently, I fixed a number of small (non-drivetrain) things on my car and I wish I knew more.

This is a nice thought, but based on my experience helping non-technical people with malware and related issues, it's rare that they learn from those experiences, and instead delegate to the nearest techy person to help them fix it. So if people are going to act that way in either case, I would selfishly rather the software just prevent them from doing stupid things in the first place, before I get that call for help.

I don't know how workable this is in reality. Most software needs some kind of interoperability to be useful.

- Network access

- Direct hardware access (such as games accessing the GPU)

- Sharing data to other software

- Consuming data from other software

- etc.

As we've seen, we wind up needing to turn a bunch of these on for most software, and while it's certainly better than giving them carte blanche over the entire system, a handful of these permissions are enough to work some skullduggery.

> - Network access

Most software does not "need" network access, it just ends up being used for telemetry, serving ads, and checking for updates you probably don't need anyway.

> Direct hardware access (such as games accessing the GPU)

"Direct", meaning they need a context handle and some shared memory to get composited by the OS. Still, I'm honestly not sure why this isn't a solved problem today. Why are GPUs not virtualizable the way CPUs are?

> - Sharing data to other software > - Consuming data from other software

Software can be grouped together and allowed to talk among eachother within a certain context without giving any given piece of it the ability to burn the world down.

You'll have a hard time convincing me that taking control away from users is a better solution.

I would think that manually granting (or revoking) specific permissions on a per-software basis equals more control, not less!

I agree that users need full control. I also think a few decades of personal computing have shown us that the defaults should be pretty safe and therefore restrictive.

Users should have to jump through a hoop or two (perhaps as simple as `sudo enable-expert-mode` in a terminal, or some such) before being able to shoot themselves in the foot.

I think that one of the reason's we're behind on this is that major players aren't putting R&D into usable clusters of user managed permissions and tools for both power users and average users to manage and introspect them is precisely because they've found a way to both shirk the responsibility and exploit their users with an App Store.

As a result, all users are imperiled.