3 ms·
The security excuse is BS. Show me the numbers for what an enormous problem this is, to justify why such an extreme measure is needed, Google! And even if it d
by mtgx 13y ago
The security excuse is BS. Show me the numbers for what an enormous problem this is, to justify why such an extreme measure is needed, Google!
And even if it does affect a ton of users, I'm sure there are other ways for Google to fix this, even if not completely. But assuming for a moment this wasn't a malicious move from Google's part, I'm still angry with the lazy decision to "just close off non-store extensions" to fix the problem.
Should I expect side-loading to be gone from Android soon, too, Google? Don't you dare!
The way Android handles this issue is the best possible compromise (there will always be a compromise between security and freedom - and that's a great thing). In Android sideloading is disabled by default, and if a user knows what he's doing, he'll enable it and do whatever he wants.
So why can't Google do the same with Chrome?! Disable sideloading by default, but still keep the option in settings somewhere. What's the big deal? Unless they have a completely different agenda behind this...
Also, I'm not sure, but do Chrome extensions work in Opera or Safari? I think it's about time we call Google on this and ask them to open up the format, so other browsers can use the same extensions. The browser shouldn't be another vector for "lock-in".