Brew for native commandline apps, Distrobox for software that runs on other distros. Boxbuddy (GUI) is an easy tool to create and manage distroboxes, and the default terminal app, ptyxis, allows you to switch distros easily from the top-left dropdown.
And more options in the Bazzite docs https://docs.bazzite.gg/Installing_and_Managing_Software/
An alternative is to bind mount the appcompat folder from your linux steam into the steam library on your windows drive.
I really hope Bazzite manages to smooth out the last few snags and use cases for dual-boot so that I can recommend it to more non-techy people without needing to explain stuff like this or the unintuitive process of importing installed windows games into Lutris.
That’s still a single point of failure. What happens if someone finds an exploit that bypasses the login process entirely?
I read this as someone bypassing the GitHub login entirely. Good luck 2FAing your way out of that one! 😜
I believe you can do this with DAVx5. I have calendars syncing to fossify with it.
PascalCase, actually.
I ran Debian Sid on my primary computer for a few years, and it broke hard several times, requiring things like booting into recovery and package dependency untangling to fix. It was years ago, so they might have better safeguards against that now, but there’s no way I’d recommend that to a new Linux Desktop user.
Flatpak is great for two groups of users: the ones who only use default settings in standalone apps and the privacy-oriented experts who know how to tweak things to their liking. In the middle is a large group of users who don’t know or care how things work, but they want that one feature an app is supposed to do but mysteriously doesn’t work with flatpak.
Even one of these occurrences is enough to make most users give up on that app or the OS entirely. I like the idea of sandboxing apps, and I use flatpak daily, but we have to acknowledge and hopefully improve some of its limitations or many users (yourself included, it seems) will consider it unusable.