I economically support other foss projects. Not just gimp really, as I have not probe whatsoever, but I have this feeling that there’s some development issues with it. It’s not normal that people have been asking for a dedicated shape tool for decades and they refuse to add it.

Godot is one of the ones I think is going to grow bigger than commercial alternatives (like Blender) for instance.

Lately every big GIMP update would be a minor version bump in other projects. Gimp 1 to Gimp 2 was some of a big upgrade. 2 to 3 not so much. Great software. But some of the things introduced in 3.0 are just fixes and patches to try to merge some of the decisions made 20 years ago with the current expectations on UX. And it’s still not there.

Yesterday I just did something very simple. Make a selection cut and copy selection to new layer. I don’t know why but things didn’t work as expected and the new layer had weird behavior, not allowing the use of the selection tool anymore and staying always on top. Not great UX for something that the user expects to be trivial.

I have never used any of those other softwares in more than a decade.

I still only use GIMP for image editing out of principle.

Still have to check every time for GIMP shortcuts because they are so counter intuitive. And there are so many counter intuitive things about it.

IMHO it have the same issue that Libreoffice. It was really made decades ago and never really updated. It’s like that meme about workflows. In their efforts not to break workflows they have gotten behind in UX compared to other software.

Also development seems to be stopping to a halt with each release compared to other more modern foss projects. I suppose it’s due an ancient codebase that’s probably really hard to work with.

I use it. It can do a lot. But UX and development speed in GIMP is not up to par with projects like Krita, Inkscape or Blender (to name a few).

Great software still. But I get why people complain about it.

You can share jellyfin over the net.

The security issues that tend to be quoted are less important than some people claim them to be.

For instance the unauthorized streaming bug, often quoted as one of the worst jellyfin security issues, in order to work the attacker need to know the exact id of the item they want to stream, which is virtually impossible unless they are or have been an authorized client at some point.

Just set it up with the typical bruteforce protections and you’ll be fine.