Much worse. I encourage you to try some properly sandboxed Flatpak apps. Here's a fun one: https://flathub.org/apps/details/com.github.maoschanz.drawing https:

Much worse. I encourage you to try some properly sandboxed Flatpak apps. Here's a fun one: https://flathub.org/apps/details/com.github.maoschanz.drawing https://flathub.org/apps/details/com.github.maoschanz.drawin... Note that the app has no access to your home directory by default, and this fact is invisible to the end user. The file open and save dialog is handled out of process by a portal, which is a service that allows an application to (with permission) poke holes in its sandbox. By tying a few different things together, this is seamless: the user gets a file chooser dialog and chooses a file, as usual. (As a bonus, it's always a native dialog). Behind the scenes, the application is granted access to read or write to that file. I don't think this would be easy to manage if Flatpak was split into a bunch of different moving parts, and I can't imagine it providing any meaningful benefit. With that said, it isn't as monolithic as folks seem to think. It's built on bubblewrap and ostree and a whole bunch of freedesktop specifications.