“Canonical only having snap releases was harmful to adoption. I liked using lxd, but uninstalled snapd (forgetting lxd used it), and my vms obviously stopped. Snap wouldn’t reinstall properly (various inscrutable errors), so I moved it all over to libvirt. I’d still be happily using lxd if it weren’t for Canonical’s snap-pushing. That’s my anecdote of one.”
-mkj
(I’m not mkj so…, but I think most users are quite against enforcement of snapd)
I removed the snap version of firefox as soon as snap started whining it couldn’t update because I was using firefox. And it even seems to start a little faster now that it’s installed through a ppa.
I only use snaps if it’s not in my repo list, not a flatpak, or not in the obs, then I’ll use snap. The LSP servers are snaps which make it easy to install, but that’s about it. Id rather avoid both and go purely with repo packages
Id like to update this to include nixpkgs as well as a last resort before snaps
yeah had same issues and moved to libvirtd and virtiofsd
I like snap.
So sorry to hear that.
It’s alright. I soothe myself with trivial release upgrades.
Having multiple release channels is amazing
Yay more work for devs
I would prefer to have multiple channels so people can test upcoming builds of my software for bugs. It would just be a matter of changing the ci/cd that alot of projects have now to publish in different places depending on the git branch
Flatpaks already work everywhere including on canonical’s OSes, snaps don’t work in containerised systems due to nesting
The biggest betefit of flatpaks was no longer having to package your software multiple times, so we don’t publish snaps for the open source projects I maintain
How Canonical seems to keep doubling down on snaps despite large push back from the community reminds me of Reddit’s API change. I didn’t see an end in sight, which is what pushed me to Fedora.
