I started using Krita, which is amazing and does lots of things I do, but the text editor when I try to resize text, it just ruins it and gets blurry sometimes. Then I found inkscape, which was good for, text and everything else worked fine, but not much of photo editor.

Inkscape is like Adobe illustrator. It’s for vector graphics and text. it’s not great for photos/pictures/pixelated things. Like, you can add those as objects to a document. But you want to edit the images somewhere else. Maybe a krita --> inkscape workflow could work for you?

I also use kdenlive for video editing, and rawtherapee for DSLR photos editing.

If you’re also just kinda exploring software for fun, I recommend trying to play around with blender for more specialized video editing. Like, if you want to add complex effects, or motion track/stabilize, whatever. It’s an extremely powerful piece of software (best to look at tutorials, idk if anyone can figure that shit out on their own). All I’ve done with it is stabilize some video (which I then used in a kdenlive project), and I absolutely haven’t even scratched the surface.

The allergy to CLI is always strange to me.

I get it. Every single other application a GUI user has used in their life: Ctrl-C = copy, and Ctrl-Z = undo. Open the terminal, and now Ctrl-C is an interupt, and Ctrl-Z is like a pause. Every terminal emulator has the option to change these keymappings. But doing that has a bunch of consequences once you start running more than basic file operations and nano. I think this is usually the first big hurdle to get over. It’s muscle memory that needs to be suppressed.

And then there’s the documentation aspect. With a GUI, you can visually look around to see what can be done in a program. With the CLI, there’s options that you just kinda have to know. There’s -h or --help, then there’s the man pages. But even just navigating the man pages brings up the previous problem of unfamiliar/unintuitive keybindings. so you could also install tldr for faster help, but the vast majority of the time, it’ll be faster to just search online.

All that being said, I prefer the CLI for pretty much everything, and think it would be interesting if there was a sort of pedagogical distro to teach the command line. Imagine a file browser that displays the underlying utilities/commands being used. Like, when you open your home folder maybe there’s a line showing ‘ls -al /home/me | grep [whatever params to get the info being displayed]’. Or, when you go into the settings, it shows you the specific text files being edited for each option. Something that just exposes the inner workings a little more so that people can learn what they’re actually doing as they’re using the GUI