GIMP's UI is what's holding it back.
If it was remotely near inkscape's usability, it would be way more popular. The script that tries to make it look like Photoshop, shows GIMP's underlying limitations.
GIMP should go straight to phase 3.
this post was submitted on 23 Oct 2023
148 points (96.8% liked)
Open Source
31018 readers
622 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
GIMP makes uncommon things possible, and common things hard. I really don't understand the mental model of people (the devs) who think the GIMP UI is intuitive. It's such a powerful, widely used program, I have always thought it was just me, not understanding some paradigm. But Photoshop is as or more powerful, and yet is so much easier to work with. And it isn't only casuals using Photoshot; professionals do too, so it's not just that GIMP is designed for power users.
I honestly don't understand how the GIMP UI can be so consistently and enduringly difficult.
Draw a straight line with GIMP. I dare you.
GIMP makes uncommon things possible, and common things hard.
Now I understand my frustrations.
Same. This is exactly how I feel about the program
Draw a straight line with GIMP.
Pencil tool, point 1, hold shift, point 2. Is it any easier in Photoshop?
Edit: yes, apparently there is a line tool in Photoshop.
Ok, that's not bad. And the GIMP tutorial pages are way better than last time I used them.
It's still a little obscure for casual users - having to remember key combinations between infrequesnt uses (was it shift? Alt? Control?) especially trips me up when working with selections... adding, removing, etc. But I shouldn't use line creation; that's pretty simple.
With default keybinds: N, left click, shift+ left click.
I started off on GIMP, decided to try Photoshop…. How… how can I come from software I have more experience with, and find it easier to work in Photoshop? As much as I want to love GIMP, damn the UX is ass
I nominate Kdenlive as the open Premiere alternative.
Kdenlive is great.
I love Kdenlive, though it's always worth keeping an eye on Openshot, Olive, Shotcut etc.
Is there any scope to allow the interoperability to work with multiple software on each end (i.e. Gimp or Krita with Kdenlive or Olive) - or does it complicate things too much?
Yes, that's the goal, am pretty sure that it's a O(n)² problem though so it's definitely a challenge.
This is definitely something that's needed, so thanks for taking the initiative to start something :)
Just to note, your front page suggests darktable as an Illustrator replacement - whereas I would have said Inkscape is the Illustrator replacement (they are both vector graphic editors) and that Darktable is for processing raw digital photographs.
Thanks, It's fixed.
Yeah, Darktable is more of a Lightroom replacement
I'm interested to see how this project turns out.
Honestly, Adobe is is one of two main reasons I have not had success switching (back) to Linux. The secret sauce with Adobe Lightroom (Classic and CC) is the ability to take pics from any device (phone, old DSLR w/manual imports, downloads) and edit from my phone, or desktop seamlessly regardless of source, all in same catalogue, with non-destructive edits sync'd bidirectionally. I also get all originals sync'd tho main computer to merge in with my overall backup strategy. None of the open source offerings have this, though I keep checking in on it every few years. I'm sure Darktable is great - it may even be better than LR, but without the easy interoperability/synchronization, it's not viable in my situation. I would not expect a solution like this to be free. I'm happy to pay for it. If Adobe offered real Linux compatibility, I'd pay for it in a heartbeat (and would gladly switch to a different company if it existed).
For video other graphic stuff, I can live with the silos and happily run Shotcut (or KDENLive) and Krita.
If it wasn't for my other windows dependency, I'd switch and get by with running Lightroom virtually, and put up with the loss of other applications/features (on the Linux host) that I can live without.
(My other dependency is NI Maschine (music production). The hardware - and the feature set I've paid for and use simply won't run on Linux. I briefly considered running it virtually in Windows but ended up giving my head a shake because of the Rube Goldberg machine I'd end up making to have anywhere close to the functionality I have now).
I'd be thrilled to switch back to Linux (I used it for years as a daily driver).
So all they have is a boilerplate script that doesn’t do anything yet?
I’d rather see this as a collaborative effort between upstream rather than a “layer” of scripts, not to mention their “phase 3” is forking upstream which we really don’t need.
I’d rather see this project’s team simply working with upstream and sending PRs / patches.
they
Am only one person :), but if anybody is interested in helping, I would love that, I can easily add you to be a member.
so all they have is a boilerplate script that doesn’t do anything yet?
Fair, I wrote that quickly as a starting point.
I’d rather see this project’s team simply working with upstream and sending PRs / patches.
Noted, am still thinking on the best way to approach this "interoperability" problem.
I love your passion but I think you published on GitHub a little too soon. Rather than pitch solutions, keep it to the problem space definition for now.
Then, reach out to the upstream developers and see what their thoughts are and how you can contribute. I’m sure there is definitely space for a interoperability library that makes it easy for any creative FOSS app to integrate and enter into this open ecosystem concept but rather than inventing it for upstream, you should invent it with upstream.
Good luck and stay this passionate - the FOSS community needs people like you!
Reproducible scripts are scripts using Nix so that we don’t have the problem of “It works in my machine”
Ok, no, thanks. This should work on all distributions with their package managers instead of needing a separate layer. The approach to first package it and then write addons is a bit weird.
That's the thing with Nix: It works on all the distros.
Distros could of course also package it themselves (nothing preventing them from doing that) but having a baseline in Nix that you can point to makes the distro's job easier here aswell. If it works via Nix but doesn't in xyz distro's package, you know where the problem lies.
That’s the thing with Nix: It works on all the distros.
… as long as you install Nix.
You could say the same about Docker, Flatpak, AppImage or even Snap. Nix is nothing special in that regard.
Nix is nothing special in that regard.
Well, with the exception that all of those tools use userns to ship almost a full userspace tree while Nix uses no containerisation whatsoever to do its job.
You can make Deb and rpm from nix packages supposedly.
https://nixos.wiki/wiki/Nixpkgs/Building_RPM_DEB_with_nixpkgs
Sticking to reproduceable builds also makes sense for development and troubleshooting, less variables to run down.
Brilliant
Just a heads up, all of the reference links are busted as far as I can tell.
I’m 99% for markdown you want to do:
Lorem ipsum dolor sit amet [link text][unique name]
…
[unique name]: website URL
Edit: removed actual URL because my Lemmy client was formatting it for markdown lol
The file is using org mode rather than markdown. I don't think GitHub has as good of support for org.
Ahh good callout, I didn’t see the filename.
Github doesn't support Org footnotes, it seems.