215
Don't use Appimages (a writeup about all the reasons they are a pain for users) (github.com)
submitted 2 years ago by to c/linux@lemmy.ml
176 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 20 points 2 years ago* (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -47 points 2 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 8 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -2 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 2 years ago (1 child)

    Are you trying to tell me creality is the only one who would ever embed a library in an appimage? Isn't that supposed to be half the point, that it comes with what it needs?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago* (last edited 2 years ago)

    No. I’m telling you that they won’t maintain it properly.

    Not when it’s a reskinned cura fork. There marlin (printer firmware- nominally more important) versions are old too… last I checked, by years.

  • permalink
  • fedilink
  • source
  • parent