Yeah yeah, AOSP and all that. Despite, Android is made primarily by Google to push Google products and most apps depend on Google services. For all intents and purposes, Android is a first party OS for Google.

Google literally owns Android tho.

From a technical point of view:

• Appimages are like MacOS .app programs. You download a random executable from a random website, that contains everything it needs to run. It’s the antithesis of the Linux way. Great for portability, awful for everything else. There are no automatic updates unless the developer explicitly bothers to implement them.
• Snaps are like docker containers. Each snap also contains everything it needs to run, but at least there is a centralized update system.
• Flatpaks are like another package manager layered over your OS. It manages its own dependency system isolated from your main dependency management. It updates its stuff pretty much like apt/dnf/pacman.
• Native are managed through your distro’s package manager, obviously.

From a feature/version point of view:

• If you have a bleeding edge or quickly moving distro, native packages are fine if you want/need up to date software. Arch users shouldn’t need Flatpaks for example. The downside is that those packages are made by the distro’s maintainers so can be anywhere from untested pre-release software (happened in Manjaro) to extremely outdated (like in Debian oldstable).
• Flatpaks/Snaps/Appimages are more and more maintained and packaged by their developers. It’s great for them as you only need to package once, all bug reports are on versions you control, and you don’t need to depend on a distro’s maintainer time and will to push updates to users. For stable distros users, this is theoretically the best of both worlds: a stable, tested OS with up to date user facing applications.

From a philosophical point of view:

• Appimages and Flatpaks are fully FOSS. Flathub is the dominant ways of distributing Flatpaks but anyone can create a competitor.
• Snaps are distributed through Canonical’s Snap Store, which is not FOSS and is vulnerable to Canonical’s corporate meddling.

My personal preference:

• Flatpaks for GUI apps, native for CLI tools
• Appimages as a last resort if it’s the only way to get a specific app.
• Snaps never.

Stop counting, you bean counter.

Bröther may I have some beåns

Seriously tho. Wefwef is incredible. Every instance should install it and give the choice to its users between the two frontends. PLus it would solve the rate limitation problems as both would be hosted on the same server.

I use Mlem ATM and I like it but Wefwef is crazy good.

Wow nice! I just replaced the Apollo icon on my Home Screen with this.

Looks great and feels like Apollo!

Oh the horror! Guess what, that’s exactly how most European countries work. We pay taxes. The rich pay a lot of taxes (not nearly enough but that’s another issue), the poor pay a lot less or almost none (except VAT, which is much more of a burden for the poor than the rich). We have public infrastructure. We have “free” public education. We have “free” public healthcare. We have “free” life saving meds. We have paid sick days. The doctors must get their license by studying and working in public teaching hospitals instead of 100k+ a year private universities. It works. Most of the public systems are still dysfunctional, but it works. No one needs to go bankrupt because they broke an ankle or their kid got the flu.

I’m so fuckin sick of this argument. “bUt mUh tAxPaYeR muNeY”. You’re actively working against your own fucking interests. Enjoy your debilitating lifelong injury that could have been entirely prevented if you had a healthcare system.

It’s meta. Their intentions are never honest.

All the large moons in the solar system are tidally locked to their planet!

Pluto and Charon are tidally locked to each other!

The earth would eventually be tidally locked to the moon too, but because it’s happening so slowly, it wouldn’t happen before the sun turns into a red giant and engulf both!