You can have sandboxing and run whatever you want. I do it every day on PCs where I, the user, can define the terms of sandboxing any appliclation I want, and not a trillion dollar corporation using sandboxes to enforce their chosen revenue streams upon users.
Yes and for you to think that is a valid argument for a consumer product is why most open source products suck for consumers and end up being about as bad as the “homermobile”.
You do realize macOS has used sandboxing by default for over a decade, right?
ChromeOS/ChromiumOS uses heavy sandboxing. Android currently uses sandboxing transparently, despite plans to iOS-ify the platform. Hell, Windows uses app isolation sandboxing these days.
All four consumer platforms let you run the software you want to and they provide sandboxing at the same time. They also let you configure sandboxes, too.
As for open source, consumer products like the Steam Deck use sandboxes, popular game launchers like Lutris use sandboxes, Firefox transparently uses sandboxing by default, as does Chromium/Chrome, anything installed automatically with Flatpak or Snap are sandboxed by default and AppArmor/SELinux works in the background automatically on most distros and are activated by default.
Saying open source projects like the Steam Deck, Firefox, Chromium, ChromiumOS and Android suck for consumers is a weird opinion, but you're free to have it.
Yes, if you bother with the rigmarole of escaping walled garden then you should be expected to navigate 20-30 permissions, which is in practice all that's necessary.
If users without that level of technical skill are pressured into making those decisions, that's because they're being mistreated.
You can have sandboxing and run whatever you want. I do it every day on PCs where I, the user, can define the terms of sandboxing any appliclation I want, and not a trillion dollar corporation using sandboxes to enforce their chosen revenue streams upon users.
Yes and for you to think that is a valid argument for a consumer product is why most open source products suck for consumers and end up being about as bad as the “homermobile”.
You do realize macOS has used sandboxing by default for over a decade, right?
ChromeOS/ChromiumOS uses heavy sandboxing. Android currently uses sandboxing transparently, despite plans to iOS-ify the platform. Hell, Windows uses app isolation sandboxing these days.
All four consumer platforms let you run the software you want to and they provide sandboxing at the same time. They also let you configure sandboxes, too.
As for open source, consumer products like the Steam Deck use sandboxes, popular game launchers like Lutris use sandboxes, Firefox transparently uses sandboxing by default, as does Chromium/Chrome, anything installed automatically with Flatpak or Snap are sandboxed by default and AppArmor/SELinux works in the background automatically on most distros and are activated by default.
Saying open source projects like the Steam Deck, Firefox, Chromium, ChromiumOS and Android suck for consumers is a weird opinion, but you're free to have it.
3 replies →
Sure I do. I sandbox what I want when I want.
So now you are expecting users to navigate hundreds of permissions and know the consequences of each one? How did that work out for Vista?
Yes, if you bother with the rigmarole of escaping walled garden then you should be expected to navigate 20-30 permissions, which is in practice all that's necessary.
If users without that level of technical skill are pressured into making those decisions, that's because they're being mistreated.
2 replies →