Tldr: the new store only supports snaps, deb support will come later. OP, please provide summary next time if you link to clickbait articles.
Deb support will come later, but:
If the same piece of software exists in the Ubuntu repository and the snap store the new store will only make it possible to install the snap version.
So the title is on point IMO.
BUT, the "new" store is based on a community project which ALREADY supports both deb and snap.
It's not a click bait per se. Even after deb support they will use only snap for applications that has a snap package and only debs if it hasn't got any snap package afaik.
Why is Ubuntu pushing snaps so hard? Is there objectively a benefit to them apart from Flatpak?
It seems like an odd hill to die on.
Snaps are used for Ubuntu's IOT distro, and also for their upcoming immutable desktop. They even ship kernel and mesa as snap, which makes updating less likely to break a system (in case of a crash while updating, user error, ...).
That's why they push snap. Canonical doesn't mainly aim to make a apps available to all distros like flatpak does. Just like now where all distros need their own packages, snap will coexist with other package formats.
For the user it's unimportant how apps are installed, as long as they're available.
There's a benefit to Canonical, the corp that maintains Ubuntu, which is that while snaps are open source tech, the server for the snap store is closed source and snap can't be configured to point at another store.
In other words, it's about centralized control.
There are some advantages to the tech itself, like live auto-updating, which is good for security-critical server apps, but over all I'm not a fan.
I believe you're completely right here, except that snapd can be configured to point to another store, though it's not very well documented.. I did find the piece of information once :).
But the thing is that the client still only supports one app backing site at a time. So if you pick another one, you lose visibility to the other store. I doubt even updates work as they should.
So it's really about building technology that is geared towards centralized control, whereas basically anyone can host flatpak packages and give ref links to them.
Canonical is just weird like that, it seems. They tend to pick something and fixate on it really hard (Eg. Unity desktop, Mir, that convergent phone thing, now Snaps) and work on it until it's almost really good, then they get fixated on the next shiny thing and dump whatever they were doing to go chase that instead.
that convergent phone thing
Tbf I think convergence could be the killer feature which pushes mobile Linux into large-scale adoption. Also Purism has its Librem 5 phone as convergent, too. It's not just Canonical.
Sooo they have ADHD and suffer with hyperfixation with the rest of us ADHDers?
Because they controll snaps. Their backend is proprietary and they do not support any other way of distribution.
Now there are some objective benefits to Snaps compared to Flatpaks, at least so I was told. Apparently they offer significantly better documentation and integrate more tightly with the system, allowing you to do more stuff with them.
This was a while back tho, I don't know where Flatpak stands today
Canonical also sells private Snaps repos for a shy amount of 30 000$ per year
https://www.nitrokey.com/news/2021/nextbox-why-we-decided-and-against-ubuntu-core
The Fedora software app has been promoting flatpaks over native packages, even not displaying that native packages are available even if they are, requiring the command line tool to access some native packages. So I don't see how this is fundamentally different.
The fundamental difference is that flatpak is a good system, adopted by many distributions.
Snap sucks and only Ubuntu uses it.
They'll do like their Unity UI, wait many years until they realize their mistake then drop it.
I hate that they also SEO'd the hell out of major search engines to show snap setup and installation instructions when anyone searches for installing a package. E.g. "arch install firefox" leads to https://snapcraft.io/install/firefox/arch which is downright dishonest marketing.
IIRC Flatpack is also FOSS whereas the Snap server software is proprietary
The big difference is that Snap is partially proprietary. For those who like Linux for its free and open-source nature and all the benefits that confers, this is an unfortunate evolution that has a negative impact on the Linux ecosystem.
And snap has other issues, such as it's very badly implemented. No sane person wants to see 100s of lop devices mounted on lsblk all the time.
Ubuntu is getting on my last nerve. At this point I'm going Debian on everything except Thinkpad, but only because it's Nvidia based and Pop!_OS just works on it.
All the servers I've spun up in the past few years have been Debian instead of my usual Ubuntu.
The last straw was kinda when I learned that installing docker via the install menu gives you the snap version instead of the normal one, with no indication that this is the case.
I never found out what's wrong with APT.
I do wish APT supported installing certain packages locally. Other than that, I'm more likely to use it than Snap/Flatpak/etc
Classic canonical move: Take community software, force snaps into it and then ship it.
Yep, I can not understand why Canonical keep pushing snaps on desktop
Because maintaining snaps is a lot less work for whoever maintains the package, upstream developers, volunteers, or Canonical. If I'm shipping software for Ubuntu and I can use snap, I sure as hell will use it instead of deb.
because they won't need to maintain it, they won't even need to maintain the dependencies, some guy online will maintain the package and it's dependency for them, whether it's updated or not, it's going to launch, that's the whole point of those style of packaging
Maybe I need to reconsider Pop OS. Last time I tried they shipped with a broken kernel, but that's probably fixed now.
Why do Linux nerds that care about this sort of stuff hate snaps so much?
Is it the concept of snaps / flatpaks that is the issue or snaps specifically because Canonical is behind them?
I know literally nothing about how they work except I installed the VLC snap and it's fine.
I couldn't install Parsec (a remote desktop game streaming app) because of a missing dependency (an old version of lib-something codec that wasn't in my newer version of Ubuntu). I spent like an hour trying to figure out how to take the 18.04 version and add it to 22.10. I don't know Linux at all so I wasn't making much progress. Someone, not the developers of Parsec, made a flatpak and it magically worked.
I was afraid that because the flatpak was made by some random guy I couldn't really trust it. I looked inside the flatpak and it's seems to be nothing except for the Parsec deb coming straight from the official Parsec URL and that libcodec thing that was causing a problem.
So from my perspective, not knowing the technical details or politics, what's the problem?
Why would a serious user want a psuedo proprietary Nth app containerization platform that sidesteps a serious incubation chain and has poor performance?
The snap store is proprietary, flatpaks handle the graphical app space better, OCI containers handle the service space better, and really high reported load times.
Flatpaks are awesome IMHO.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0