I was quite happy with that, actually. Given the options available for installing an application, what would you have preferred? If it had been a GitHub repos

I was quite happy with that, actually. Given the options available for installing an application, what would you have preferred? If it had been a GitHub repository with a releases item, it would have either been a tarball'd source I have to compile (I run Linux), an RPM file that might-or-might-not work (I run openSUSE and Fedora/Redhat RPMs are more common and hit/miss on openSUSE), instructions on how to apt-get or yum install it -- no openSUSE zypper commands (though, yum instructions often work depending with the same hit/miss ratio as RPM installs). An improvement would have been if it was code-signed in some verifiable way (I'm not sure if it was or wasn't -- I wasn't paying a lot of attention when I launched it in this virtual, TBH), but the reality is that if you want to run code, it has to be in a binary format of some kind whether you compile it yourself or it's compiled for you, and even in the case of self-compiling ... it's not like you're going to do a line-by-line audit of the code looking to ensure they're not trying to win an underhanded C contest. At least an AppImage file can be run in a sandbox, and it is a very pleasant way to get a working binary on a Linux host. It didn't require root privileges to install or execute (that would have caused raised eyebrows, here).