Like many, I have had my fair share of frustrations with snaps. Already considering moving away from Ubuntu, but not sure where to go next. Is Debian a good option? I use Linux both personally and professionally, so while I do like to tinker with new stuff, I also need some stability. I've used rolling-release distros in the past and its something I'd like to try again. Maybe Manjaro?
Ubuntu stops shipping Flatpak by default
241–250 of 624 posts
Re: Ubuntu stops shipping Flatpak by default
#242Earlier quoted context omitted.
I wish all software could provide portable binaries. However, compiling portable binaries is hard. Not many developers have the skill.
Indeed. This seems like a tooling issue, and one that strikes me as more worthy of community attention than reinventing the package manager for the nth time.
Re: Ubuntu stops shipping Flatpak by default
#243Wow they're still pushing snaps, the project with some the worst engineering I've ever seen. - Extremely slow at doing anything, even the most basic commands. - Ridiculous auto-update mechanism (you can't even disable it wtf). - Random, nonsense limitations (why can't I open dot files and dot directories???). So terrible that for most apps that I installed with snaps I end up installing the deb version later on. What…
My favorite experience with snaps is Firefox just closing in the middle of doing something because it wanted to update, and it didn't even bother to check if I was using it first.
Re: Ubuntu stops shipping Flatpak by default
#244Like many, I have had my fair share of frustrations with snaps. Already considering moving away from Ubuntu, but not sure where to go next. Is Debian a good option? I use Linux both personally and professionally, so while I do like to tinker with new stuff, I also need some stability. I've used rolling-release distros in the past and its something I'd like to try again. Maybe Manjaro?
Re: Ubuntu stops shipping Flatpak by default
#245Earlier quoted context omitted.
Hot take: package distributors are 'fake jobs' that don't need to exist, or exist only for the make-work of packaging. Tools like flatpak, snap, appimage, containerization, etc. have made the need for adapting software to different distributions unnecessary.
Yeah, if you don't mind hugely increased start-up times, RAM usage and less curation and more crap, sure no need for package distribution. I personally do mind very much. Just the differences in startup times between apt and snap applications are huge and I would absolutely despise working with such a sluggish system. I would rather build everything myself from source if forced to.
Re: Ubuntu stops shipping Flatpak by default
#246Wow they're still pushing snaps, the project with some the worst engineering I've ever seen. - Extremely slow at doing anything, even the most basic commands. - Ridiculous auto-update mechanism (you can't even disable it wtf). - Random, nonsense limitations (why can't I open dot files and dot directories???). So terrible that for most apps that I installed with snaps I end up installing the deb version later on. What…
Snaps are getting me off Desktop Ubuntu after 12 years of happily using it.
Re: Ubuntu stops shipping Flatpak by default
#247Re: Ubuntu stops shipping Flatpak by default
#248So, for a developer, what's currently the best hassle-free desktop Linux Distribution?
Re: Ubuntu stops shipping Flatpak by default
#249Earlier quoted context omitted.
Same here off Ubuntu and onto centos/fedora rpm dnf world
Glad you have something sorted out. Just interested: why not Debian? i.e. still deb based distro? I'm guessing the poster above you wants recent package versions as they went to Arch.
I usually run Fedora rather than Arch though, because in my limited experience with Arch it really doesn’t like to not be booted into for extended periods of time — if you do that the piled up updates are much more likely to break somehow or things like required config changes will slip through the cracks, whereas I have yet to experience this with Fedora.
Re: Ubuntu stops shipping Flatpak by default
#250Earlier quoted context omitted.
There are plenty of projects to semi-automatically produce packages for a large number of distributions starting from just a git repo of the software to package. Sure, packaging software is a bit of a thankless task, but with enough automation, packaging thousands of bits of software on every git commit should be doable by just a few volunteers.
What I would like to see is: 1) a unified database for package names (it's all unnecessarily ad-hoc right now, with different distros having different policies for capital letters, whether libraries are prefixed with "lib", whether python packages have "py" or "python" or "py3" etc... 2) a standard format for declaratively describing how to build a package. Basically, we have FreeBSD ports, Arch PKGBUILDs, Void templ…