This is the crux of the matter.
Maybe conceptually you will be able to run some kind of open operating system with your own code, but it will be unable to access software or services provided by corporate or governmental entities.
This has been obvious for some time, and as soon as passkeys started popping up the endgame became clear.
Pleading to the government definitely can't save us now though, because they want the control just as much as the corporations do.
> passkeys started popping up the endgame became clear.
This logical leap puzzles me, as it is completely unrelated to HW lock-in and a rather generic medium.
This is more of a case of OP diverting a topic to shove in his pet peeve on technology they don’t like or understand.
Ironically, if everyone adopted passkeys (the real deal tied to secure enclaves or TPMs), then Android malware could not steal your credentials through any kind of social engineering.
> Maybe conceptually you will be able to run some kind of open operating system with your own code
Why do you think they would even allow this? If you think that governments don't have the incentives or the means to criminalize running non-approved OSes, or the unauthorized use of non-approved hardware, you're insufficiently cynical.
Should have made open-source components in some key nodes of the ecosystem popular and profitable. But that was a tall order.
> as soon as passkeys started popping up the endgame became clear
That's why I'm 100% against passkeys. I'll never use them and I'll make sure nobody I know does.
They're just a lock-in mechanism.