I guess I can somewhat formalize all of my hypothetical solutions to various software-relates problems as "restrictions bring power"
My solutions to desktop software include more restrictive permissions, high level system interfaces, enforced interface designs via system APIs, strict resource limitations, etc.
My solutions to browsers include strict resource limitations, more restrictive APIs and legal enforcement of certain patterns.
My solutions to video games include enforcing smaller budgets, usage of system APIs and, of course, never letting a video game install something with high privileges.
And this same mentality can sort of be extended to many more things. I guess I've found that third party developers aren't necessarily trustworthy and that it's much better to restrict software into the shape that fits your system while educating the user as to what can and can't be trusted rather than letting your system devolve into a mess of windows with different shapes and interfaces doing different and contradictory things and nothing ever working smoothly.
In a way, this mentality of using restrictions is also how I approach a lot of art. I'll always favor a story that manages to say something complex with few characters, few locations and few plot points rather than one with a message just as complex but with significantly more moving parts. Less is more in many cases, and limitations force you to be genuinely creative and think a lot more about what you do and whether it's needed or not and ultimately limiting yourself will often result in a better end result.
