Support AppImage

[corygalyna]

Description

Since AppImage is quite famous across Linux OS.

Expected Behavior

AppImage is available.

Current Behavior

AppImage is not available.

Associated Data Files

No response

[hollowaykeanho]

I'm pessimistically reluctant to support it mainly because:

1. It's better to encourage others to build static binary (signed or unsigned) rather than an ISO wrapper that relies heavily on libfuse to do the single executable effect. It has been lying to people that "it's a single executable" when it's not. Worse of all, it attaches a system dependency onto an independently executable binary.
2. Unlike Flatpak or Snapcraft, it's not being Sandbox-ed, which is something a next-generation package ecosystem should inheritly have.
3. It encourages folks to randomly download a binary executable across the Internet without something kind of built-in system for authenticity checking before first unpacking.
4. @probonopd intentionally discriminate me in the AppImage forum (see screenshot below) and I'm also aware of @probonopd work at OBS community. With that kind of support and drama, I rather not get involve at all.

[corygalyna]

Ahh isn't it unfair to the community?

[hollowaykeanho]

Don't blame me. I did try to reach their community and founder for help but they shut me out like sinophobic or something. If we're proceed with this idea and bump into their tech problem, we're completely on our own for a tech we're not responsible for. It wasted me a month just to read through their codes for understanding AppImage.

The whole point of this project is to make .deb, .rpm, .ipk, .flatpak, .tar.xz, .zip, homebrew.rb, containers (Docker & Podman), and .nupkg (choco) packaging and releasing processes way seamless from the get-go. Place all of them onto the table together and you'll realize there isn't much value appimage is bringing onto the table; left alone being passive aggressively assaulted by them from the start.

I'm sorry Cory. This is the way to go. For the betterment of Linux ecosystem:

1. use .tar.xz, .zip, or .ipk for direct binary access.
2. use .deb, .rpm, homebrew.rb (brew) and .nupkg (choco) for legacy distribution system.
3. use .flatpak for sandbox + all-in-one next generation distribution system.
4. use docker or podman for containers.

[corygalyna]

sigh. Okay.