31–40 of 84 posts
Earlier quoted context omitted.
Interesting anecdote. What did you end up doing? Did you just leave it as-was?
S?he probably listened to the keyup event instead.
Earlier quoted context omitted.
This would effectively kill innovation. There is a reason you can't do half the things you do on a laptop on a phone unless you root said phone.
The idea is not to prevent programs doing those things, it's to prevent programs doing those things without user permission .
I don't know of any.
".. Heck, even the $300 chromebook we recently got has 16GB of RAM.. " I don't think sth like that exists.. which one is it?
Earlier quoted context omitted.
The idea is not to prevent programs doing those things, it's to prevent programs doing those things without user permission .
Is there (or was there every) any OS app store that allowed an app to go trawling through another apps's memory? Or if you don't want to be that radical, one that at least allows overlays. I don't know of any.
I think both of these features require explicit manual permissions (i.e. having to go to the system settings and whitelist the app) to be enabled. Also Android permission dialogs refuse to pop up if there is an untrusted screen overlay (which meant that my experience with Lux when with other apps' permission dialogs involved either manually disabling the virtual screen brightness adjustment or having it automatically disabled temporarily, which resulted in unpleasant surprises while using the phone at night).
Earlier quoted context omitted.
This would effectively kill innovation. There is a reason you can't do half the things you do on a laptop on a phone unless you root said phone.
I'm not sure I buy that requiring user opt-in to camera access is why the Mac app ecosystem is is much larger than that of iOS. Can you elaborate on what apps/innovations would become impossible because of a mandatory opt-in? I cannot think of any...
I'm not against sandboxing, but if there should be a way to say i know what i'm installing, go with it. Otherwise you will say good bie to new ways of debugging, alternative drivers, unusual way of routing network packets, innovative UI interactions that are not part of the standards widgets, or anything you haven't think of yet.
The computing experience you have today is the result of all the stuff we fiddle with for the last 30 years because it was allowed to. It would be foolish thz big players invented most of it.
Earlier quoted context omitted.
Interesting anecdote. What did you end up doing? Did you just leave it as-was?
S?he probably listened to the keyup event instead.
Earlier quoted context omitted.
This would effectively kill innovation. There is a reason you can't do half the things you do on a laptop on a phone unless you root said phone.
There is also a reason I can do 99% of the things I do on a laptop on my (totally sandboxed, not rooted) iPad Pro.
Earlier quoted context omitted.
S?he probably listened to the keyup event instead.
You'd have to listen to both, right? Otherwise it'd be the same issue when the user tabs into the password input rather than out of.
You could listen for the keydown, but you wouldn't hear it, so you may as well ignore what you can't hear.