Appimages totally suck, because many developers think they were a real packaging format and support them exclusively.

Their use case is tiny, and in 99% of cases Flatpak is just better.

I could not find a single post or article about all the problems they have, so I wrote this.

This is not about shaming open source contributors. But Appimages are obviously broken, pretty badly maintained, while organizations/companies like Balena, Nextcloud etc. don’t seem to get that.

  • @hperrin
    link
    76
    edit-2
    9 months ago

    I agree with this, but as an app developer, can I just say, Flathub’s documentation is an absolute abomination. It is so bad, that I’ve tried 3 times to publish an app and have given up each time. I can build a local Flatpak just fine, but getting it on Flathub is just so convoluted and bad.

    AppImages are ridiculously easy to build and distribute, just a pain to actually use. And even then, they’re not that much of a pain.

    • @[email protected]
      link
      fedilink
      79 months ago

      If worst comes to worst you can just distribute your .flatpak file directly, as you would with your app image

      • @[email protected]OP
        link
        fedilink
        29 months ago

        This would tick a lot of issues but please dont do that. People will get used to it and suddenly malware is possible again.

    • @db2
      link
      -359 months ago

      Try getting Creality Print to run without manually updating components of the appimage. I’ll wait.

      • @hperrin
        link
        279 months ago

        This has nothing to do with my comment.

        • @db2
          link
          -499 months ago

          Uhh ok pal, sure thing.

          • youmaynotknow
            link
            fedilink
            20
            edit-2
            9 months ago

            Bro, a developer (which I am not) voiced his opinion. What’s the need for the toxicity? Isn’t it better for everyone if we all ask questions or provide our opinions respecting others? This is the reason why ANY difference of opinion ends up turning into a heated and useless argument. If you have something to counter what he said, by all means, bring it to the table. @hperin didn’t say anything out of place.

            • @db2
              link
              -489 months ago

              I think you’re both on something either really good or really bad. I added to the sentiment about appimages and you’re both too busy sniffng your own farts too actually read the very short thing I wrote. You’d rather create a narrative in your own head about what a big meanie I am. So be in it then.

              In conclusion, screw both of you, you’re blocked. I have only marginally more patience for stupid than Linus does and you’re both well past that. Have a nice day.

              • FuglyDuck
                link
                English
                89 months ago

                One specific implementation by a terrible company that can barely manage to check quality control on their actual products isn’t a very good example of appimage’s problems.

                Not saying they don’t have problems. But having seen creality’s version of Marlin, I gotta say, I’d be willing to bet they rebranded something, but using vastly out of date versions.

                Probably should switch to simplify3d, prusa or cura.

                • @db2
                  link
                  -29 months ago

                  While you’re not wrong, the problem I was referencing is an outdated library embedded in the image. It makes the whole app crash and it could happen to any app.

                  • FuglyDuck
                    link
                    English
                    39 months ago

                    That’s a creality problem. Not an appimage problem.

                    They’d have a just as shitty flatpak or whatever else they used; because that’s how the company is.