<span style="font-style:italic;color:#969896;">/*
</span><span style="font-style:italic;color:#969896;"> * Make /sys/kernel/notes give the raw contents of our kernel .notes section.
</span><span style="font-style:italic;color:#969896;"> */
</span>
This may be a little bias but this is my understanding:
Flatpaks were the solution for reducing the duplication in Appimages and providing an automated way to do security updates. Flatpak got a chance to learn from Snap.
Snaps are basically a proprietary approach to creating and distributing Appimages that were created prior to the current Appimage tooling. They got to learn from the first generation of Appimages and decided to deviate from them early on.
Appimages were a stupid simple approach to a complex issue. Initial tooling was rough though and a lot of people, while they liked the idea, hated the requirements. Basically setting up an Ubuntu 18.04 environment for packaging was the only way to guarantee a truly portable image.
It left room for improvement and so decisions were made to try and fill that room. They were never bad, and devs weren’t really trying to do anything other than simplify the creation and distribution of existing Appimage functionality.
I still think flatpaks are the closest to the ideal solution but again, I’m biased.
This is where someone tracks down an upgrade path chart you didn’t know existed and points out some goofy intermediary release, not an lts for some reason, that you were supposed to upgrade to first…
If I recall correctly, the whole suite was sold to a company that has a history of acquiring existing tools just to park them in maintenance mode and fill them with ads.