4 ms·
Wanting to run programs without them being able to screw around with one another is a use case... and it's more a more common, fundamental one than wanting to r
by Hizonner 4y ago
Wanting to run programs without them being able to screw around with one another is a use case... and it's more a more common, fundamental one than wanting to run remote video conferencing or whatever.
More to the point, you can always add the ability to do stuff like that, when you have the time to do it in a way that lets the user decide what should and should not have any given kind of access. On the other hand, if you start out by just letting everything run amok and then try to add controls later, assumptions will get changed underneath existing programs. That pretty much always makes things break in ugly ways... if it's even possible to do it at all, which is not guaranteed if you didn't think hard before you designed the function to begin with.
- michaelmrose 4y agoRemote video conferencing is vastly more popular than Linux at this point with work from home, remote doctors appointments, and travel issues. It's now something your 70 year grandmother who doesn't understand computers does.
- Hizonner 4y agoMy 70 year old grandmother (who'd only be about 10 years older than I am, which is a bit strange...) ALSO runs other programs all the time, and does not expect them to interfere with one another in confusing or malicious ways.
- michaelmrose 4y agoIn 19 years I've never seen an application interfere with another in confusing or malicious ways. I don't want to give up actual functionality to solve imaginary problems.
- Karunamon 4y agoWell, I have, but those were anti-viruses and are commonly understood to be crap outside of enterprise endpoint protection (And usually even then too) :)