this post was submitted on 13 Feb 2024
1775 points (97.0% liked)
Memes
45152 readers
2772 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The right design decision isn't necessarily the best for a specific use case. Making the system overall rigid and strict by default makes the whole thing more manageable. Adding features like "user initiated opt-in shared filesystem access for sandboxed apps" increases complexity, hence cost and maintenance burden and likelihood of bugs. Not to say this feature isn't worth it, but it's necessary to accept some rough edges in some use cases.
More manageable for who? Certainly not me. Which, considering I own the device, is bullshit. Desktop apps have had this figured out for decades.
The people who build the device and software ecosystem you take for granted.
They're not taken for granted, they are compensated by the corporations I'm purchasing the device from. Again, these problems have already been solved on desktop for decades. They're not breaking new ground here.
You're taking for granted the requirements that need to be met in order for the device you're purchasing to be technically and commercially viable. It needs to work, it needs to be safe, it needs to comply with privacy regulations and so on.
Managing complexity with containerization and sandboxing is occurring on desktops too. It's more mainstream in the mobile ecosystem because of essential differences in the ways users interact with phones versus desktops.
Yes and if I want something in a container I do so. It's my choice. I'm not forced into it by design choices made based on being too cheap to go beyond the absolute bare minimum.
Just go write your own Android then?