I know some webhosting provider that used one VM for every user. Now they moved to using this. Firstly low resource usage. If one uses ZFS or btrfs then one can save storage as in common bits are not duplicated across system containers. Note this is a system container - not traditional container. This one can be rebooted to get the previous state. It is not ephemeral.
I would assume apps that are non-geek oriented will do quicker adoption. In my experience, many people are looking at passkey like a
- Password manager that is automatically working fine on their phone
- Apple or Google takes care of everything. And users think of it like 'Sign in with Google/Apple equivalent'. Press fingerprint/face-ID and all just works.
Only PITA I expect is that banks type dinosaurs will screw up this (like they did with 2FA - with custom apps and non-standard implementations). I wish W3C would some way ban these but banks are somehow escaping standards.
Roflmao... Okay, I've only been here a wee bit but even I recognized the username despite having memory issues (ironically here, caused by being hit no less than 5 times as a pedestrian and cyclist)....
Does this mean the legal team do not understand tech? How come a company like Google/YouTube have no checks-balances when sending things like this? Or do the top-level not have powers over legal team?
This gets worse when reading developer documentation
- Github does not allow for 'web' VSCODE to have English (if I use non-English OS locale or browser).
- Google - developer sites (API) translate it to local language. While one can chane it; for reasons unknown this reverts back if one logout and relogin. BTW, most EU devs reading developer documentation still want to read things in English, as it helps better communication with rest of the world.