> What should Google do when a change they are making to protect regular less-technical users breaks functionality needed by more advanced users?
Put it behind an USB ADB only toggle and be more transparent to avoid slippery slope?
Put it behind an USB ADB only toggle and be more transparent to avoid slippery slope?
I don't think OS vendors should be expected to keep people from doing dangerous things. A warning label saying "hey that's dangerous because..." is reasonable, but anything more and they're trying to be my sysadmin against my will.
These are sold as consumer devices and not general computers. It sounds like you want something different. They’re selling cars and you want a motorcycle.
More sysadmin-as-a-service type stuff is fine as long as the opt-out is easy. This isn't. I'm upset about the rug pull.
You never know though. Sometimes things go the other way. When the iPhone launched there was no way to create apps for it or install third party applications except as web apps.
The real problem is that prior to verification, Google can't ban ICE tracking apps (or whatever the next problematic government doesn't like) from Android, and after verification they will be able to for most users.
They say they won't do that. I might even believe the people currently running things won't do that, but they will be incentivized to do that in the future, and incentives are much better at predicting outcomes than intent.