Being lightweight, quick to start with just the essential features is what I appreciate in both.
It's just that for my simple uses (stitching bitmaps together, resizing, getting color values, pixel-perfect alignment, working with multiple buffers, turning toolbars on/off, editing in layers) Pinta feels much clumsier than its big brother.
Let Krita be your new friend. https://krita.org/en/
I use four graphics tools in Linux.
1) Inkscape (Vector paint program) I also use it on Windows though I have a Adobe license
2) Gimp (My go to raster image editor)
3) Krita my go to paint program and not really for raster image editing
4) Aftershot Pro - My raw image and editing tool for quick photo edits
Krita is more comparable to Corel Paint then to Photoshop or Gimp.
• It's more packages I need to download. Doubly annoying because 95% of the packages are just "thin wrapper around foo, because we're too hipster to use libraries directly like peasants".
• It installs system-wide services I have to disable/mask just so other programs don't mistakenly use them because they think I run KDE and they have to integrate into it.
• Oh wait, I can't disable some of these, because Krita itself needs them and now I need to figure out how to make them play nice with my desktop aaaaaarggghhhh
"Number of packages" is not a very meaningful metric. The combined filesize isn't that large (not by the standards of an image editor anyway), and under any modern package manager installing a package with dependencies is no harder than installing one without.
> It installs system-wide services I have to disable/mask just so other programs don't mistakenly use them because they think I run KDE and they have to integrate into it.
Really? KDE tends to be a well-behaved crossplatform citizen IME (unlike Gnome) and not rely on anything system-wide. (There was some horribly ill-advised semantic nonsense in KDE 4, but I don't think it ever affected Krita).
But I can't agree on the first one.
I have not checked what these exact thin wrappers are, but most of the time thin wrappers are really useful for testing and switching to another library without being tangled in the old one.
It pretty much follow the "D" (Dependency inversion principle) in the S.O.L.I.D. principles: "Depend upon Abstractions. Do not depend upon concretions.”.
Again, I have not checked the KDE libs you talk about, so I'm assuming this is what these wrappers are used for.
(Source : https://en.wikipedia.org/wiki/Dependency_inversion_principle & https://en.wikipedia.org/wiki/SOLID_(object-oriented_design) )
It's worth taking another look if that was something that put you off in the past.
75 MB appimage download then! https://krita.org/en/item/krita-3-0-released/