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.

Today I’m making yet another variation of my witbier, this time with kweik and lemon balm.

Oh thanks, I’ll check it out.

I tried running the tgz a few months ago. It needed a shitload of deprecated python dependancies, I’m not well versed in python so after the 10th pip install I gave up.

Version 4 is unfortunately closed source and paid.

I went to my first IRL GP in Monaco this year, and the F1s were definitely the “quietest” of the lot. Still painful after a while, but not as much as the other series.

The Porsche Cup cars are obnoxiously loud. The F2 car engines sound dull but downshifts sound like gun shots.

I think if you want ear splitting sound levels and variety, go see a GT3 race.

Hardware and software integration are, for me, the major selling point of Macs and MacOS. If it makes you feel much more comfortable, go for it.

TBH I did the other way around. Ditched windows for Macs around 2005. Eventually got tired of my super outdated macOS on an 10yo laptop a few years ago, was working with Linux already for more than a decade, and I was already using FOSS software for most of my use cases, so I made the jump to Debian Gnome. Everything felt natural. I tend to organize my workflow around what works tho, so YMMV.