Windows 10 is close to being dead now, with support ending this year. So why not try out Linux? Instead of getting a whole new system and having to deal with the increasing amount of AI junk and adverts in Windows 11.
Damn, that’s a hell of a high effort response, thank you for the info!
I’ll try another SilverBlue install, probably a bluefin variant you mentioned. It definitely sounds like I need to unlearn a lot of the info I’ve picked up over the years, including avoiding flat packs (or was that snap?). Not sure what toolbox is, but I expect I’ll have to look into that in due time.
The biggest downside to Flatpaks is that they’re kind of containers. That’s obviously also they’re biggest upside. But with that isolation comes some bloat compared to rpms directly installed, some don’t integrate as cleanly with the host OS, etc… The Universal Blue images ship with Flatseal and Warehouse which help manage those Flatpaks. For example, if you want to add an external library to the Steam Flatpak, you can use Flatseal to allow the Steam Flatpak to access that directory. By default Steam sandboxes itself to just its own ~/.var area.
A word on toolbox. It’s really cool and it comes with Fedora Atomic spins. However, it was forked and the fork is called distrobox and is miles better. So much better that it’s my opinion that we at Red Hat should deprecate toolbox and just embrace distrobox. What is it? It’s really just a wrapper for podman. It sets up containers to act kind of, sort of like VMs or LXC system containers, but it mounts your home directory inside the container. You can share apps between the distrobox and the host. The idea is that you can create a distrobox for whatever thing you’re doing, install all of that thing’s dependencies, and work from your home directory, but never actually touch your host installation. Kind of like a devcontainer for your system.
Snap is the one we poo poo. Canonical is always going to Canonical. Just like when they tried to make the Unity desktop (which I actually preferred) and the Mir compositor, the community had already settled on GNOME 3 and Wayland. This is sort of snap vs flatpak. Last I knew snap used a proprietary, hosted by Canonical, backend. That’s a big no from me. I’m not staunchly open source or nothing, but there is just no reason for Canonical to be making proprietary anything.
If you can’t tell, I’m stoked about the immutable future of Linux.
Damn, that’s a hell of a high effort response, thank you for the info!
I’ll try another SilverBlue install, probably a bluefin variant you mentioned. It definitely sounds like I need to unlearn a lot of the info I’ve picked up over the years, including avoiding flat packs (or was that snap?). Not sure what toolbox is, but I expect I’ll have to look into that in due time.
The biggest downside to Flatpaks is that they’re kind of containers. That’s obviously also they’re biggest upside. But with that isolation comes some bloat compared to rpms directly installed, some don’t integrate as cleanly with the host OS, etc… The Universal Blue images ship with Flatseal and Warehouse which help manage those Flatpaks. For example, if you want to add an external library to the Steam Flatpak, you can use Flatseal to allow the Steam Flatpak to access that directory. By default Steam sandboxes itself to just its own ~/.var area.
A word on toolbox. It’s really cool and it comes with Fedora Atomic spins. However, it was forked and the fork is called distrobox and is miles better. So much better that it’s my opinion that we at Red Hat should deprecate toolbox and just embrace distrobox. What is it? It’s really just a wrapper for podman. It sets up containers to act kind of, sort of like VMs or LXC system containers, but it mounts your home directory inside the container. You can share apps between the distrobox and the host. The idea is that you can create a distrobox for whatever thing you’re doing, install all of that thing’s dependencies, and work from your home directory, but never actually touch your host installation. Kind of like a devcontainer for your system.
Snap is the one we poo poo. Canonical is always going to Canonical. Just like when they tried to make the Unity desktop (which I actually preferred) and the Mir compositor, the community had already settled on GNOME 3 and Wayland. This is sort of snap vs flatpak. Last I knew snap used a proprietary, hosted by Canonical, backend. That’s a big no from me. I’m not staunchly open source or nothing, but there is just no reason for Canonical to be making proprietary anything.
If you can’t tell, I’m stoked about the immutable future of Linux.