Why do you need to have two package formats that do the same thing installed by default? If you could install snaps and flatpaks both from the same store you could have 2 (or 3 if you also installed the .deb) copies of the same app, like steam etc installed, and user sessions and games set up on one wouldn't be launchable from the other because they all store their state and config in different locations - the only way to know what config your program is launching with would be to inspect and rename the launcher scripts. If you are intending to support naive users this is the absolute worst case scenario. It would be like debian including pacman by default as well alongside apt for maximum user accessibility confusion.
Do keep in mind that “not installed by default” is not the same as “not available to install at all”. To this end, Flatpak continues to be available in the Ubuntu repos, and users of Ubuntu flavors are free to install Flatpak
APK isn't a closed source format just because Google operates the main store.
If there was community effort someone could spin up their own snap store, this person did it https://forum.snapcraft.io/t/lol-an-open-source-snap-server-implementation/27109 - problem is, it would serve no benefit because you would have to create your own signing authority and patch snapd to use those assertions instead - and then you are still relying on a central authority to vet and sign releases and frankly I would rather have my software signed by canonical than someone random guy operating their own snap store
Which is why I phrased my above comment in the very precise and deliberate way I did.
You don't need to interface with canonical's server to use snaps, you only need to do so if you want snaps that have been approved by and signed by canonical. Anyone can create a snap and privately distribute and install it, and every part of that process is open source.
Problem with that is that when you click a link in the teams PWA it opens in edge rather than your default browser. I just use the unofficial teams electron app
I'm aware, I'm just saying that if you make $5 worth of hummus you are going to be spending about the same amount (if not more) on pita. Compared to, e.g. a baked brie, where you need $3 worth of dipping instruments to consume $10-15 worth of dip
That sounds like an issue with google play store, or perhaps you bought "sync for Reddit pro" (the app) in addition to the "remove ads" (in-app purchase on the free app)
I bought redditsync (what it was initially called before Reddit made everyone rename their apps) for $3-4 and used it for a decade without issue
To be fair, in the rest of the world there aren't tipped establishments competing with next door no-tipping establishments. People are bad at math, a menu of $13 + tip options seems cheaper at a glance than a menu of $15 no tip options. We are talking about the country where the 1/3rd pounder burger failed after all
The curl that ships with apt is ubiquitous enough that I trust doing sudo curl xxx yyy more than enough if it means avoiding typing curl xxx /tmp/yyy && sudo mv /tmp/yyy yyy
Sort of fine is even an exaggeration. I gifted my GF don't starve together the other week and steam froze and crashed 3 times just trying to log in. After an hour of trying and failing to get to the library page we just gave up. This is on the current model MBP
Why do you need to have two package formats that do the same thing installed by default? If you could install snaps and flatpaks both from the same store you could have 2 (or 3 if you also installed the .deb) copies of the same app, like steam etc installed, and user sessions and games set up on one wouldn't be launchable from the other because they all store their state and config in different locations - the only way to know what config your program is launching with would be to inspect and rename the launcher scripts. If you are intending to support naive users this is the absolute worst case scenario. It would be like debian including pacman by default as well alongside apt for maximum user
accessibilityconfusion.