3 ms·
Oh god. What awful, awful ideas you have. Where to begin? Okay, let's start with: How on earth will you ever know what your machine is actually doing? Do you
by negativity 13y ago
Oh god. What awful, awful ideas you have. Where to begin?
Okay, let's start with: How on earth will you ever know what your machine is actually doing?
Do you just run around downloading random .sh and .bat files and say FTW and run them without considering what they might contain? I mean, it's not like the app market actually tells you what an app really does.
All you're ever informed of is those broad, vague categories of behavior an app might engage in. GPS, Camera, Microphone, Intercept phone calls, Storage access... give them all away and run the app. Millions, if not billions of operations frittered away, on your dime, for someone elses benefit.
Sounds like a great idea. Just let everyone hijack your system, and do whatever they want, and don't stop to think about who or why.
...but the EXPERIENCE, man. Just think about the EXPERIENCE!
...or you could just read some words on a page, and look at some pictures, and it stops there. You get to retain a degree of control over your machine. You pretty much know it's only doing a few simple things, and you get to use the rest of your machine for your own purposes, why not?
- astrodust 13y agoHave you heard of sandboxing? I guess not.
- negativity 13y agoYes, well, the concept of sandboxing is wonderful, but that's all it is. A concept. An idea. A design pattern. It's not guaranteed to be effective. Many people will go about implementing many different types of sandboxes many different ways. Yeah, browsers sandbox their active content, and mobile operating systems sandbox their apps, but so what. Why should everyone acquiesce to being continually haunted by ubiquitous background processes that are constantly monitoring their every zoom, tilt, scroll, highlight and twitch? Why?