AppImageUpdate VS gimp

There's an updater for appimages https://github.com/AppImageCommunity/AppImageUpdate

AppImages can contain update information (and even support partial updates using zsync), check out https://github.com/AppImage/AppImageUpdate.

https://github.com/AppImage/AppImageUpdate this only works if the application has information regarding where to fetch the update from...

It would be very nice and handy if we could easily update Tutanota Linux desktop app. Luckily, since it is packaged as an AppImage, there's an easy-to-integrate utility available just for that.

It's not centralised, not like Snap with SnapCraft, not even like Flatpak with it's 'not technically but kinda is in practice' Flathub repository. Anyone can make an AppImage, anyone can host an AppImage, anyone can download and run an AppImage, anyone can implement AppImage integration in a distro, and there's even a nice system for automatic updates for AppImage which again is nicely decentralised.

Some have built-in. some not. Btw I considered AppImageUpdate , but it would become re-install a full new app

The fact is that the delta update system via Zsync and appimageupdatetool are real solutions to the problem, but too many developers do not implement it in their AppImage, myself included.

Btw, regarding Flatpak, I've had multiple issues related to mouse cursor, fonts, and local folder access - all related to the sandboxing of apps, all resolvable, but potentially a problem for a non-technical user. I've had much better experiences with AppImages, but I don't know if they have a graphical app store like interface; even the AppImageUpdate idea is still catching on.

GIMP: C, not C++

GIMP - https://gitlab.gnome.org/GNOME/gimp

GIMP

How are they implement? https://gitlab.gnome.org/GNOME/gimp https://github.com/figma

As u/schumaml said already, we have an issue tracker: https://gitlab.gnome.org/GNOME/gimp/

The former might be something you want to report as an issue at https://gitlab.gnome.org/GNOME/gimp, with the XCF file used for your cover image - or a mockup exhibiting the same issue - attached.

As Gimp is open source, I already had a look in the source code but it's written in C, which is different enough from C++ or C# that I have a rather difficult time understanding it, at least in terms of project structure. I'm pretty sure I found the handling of the tool itself in gimpoperationcolorize.c but I don't know where to go from here.

> Gotta be real, Gimp's not that far off from just one guy (https://github.com/GNOME/gimp/graphs/contributors)

GitHub only shows people with an email address linked to a GitHub account in that chart; the last time I checked it was 4 or 5 people working on it regularly, which is still a very small team (none are working on it full-time) so your point still stands (it's a point I've made myself a few times before when people compare GIMP to Photoshop or the like).

Maybe not the best example. The one on github is just a mirror of this one.