4 ms·
I haven't used GIMP in a while but I had great experience with Krita, even with my display tablet it all "just worked".
by ehnto 7mo ago
I haven't used GIMP in a while but I had great experience with Krita, even with my display tablet it all "just worked".
- archi42 7mo agokrita looks great! I'm not a hugely creative person, so last time I spent time to learn a graphics tool that was gimp in the early 2010s. But I used krita last week to test my convertibles's pen (Dell PN7552W, on Linux of course). Pleasant experience overall, and utterly amazing how far krita came in the last decade.
- mikkupikku 7mo agoYes, Krita is definitely my preference, and aseprite for pixel art work (not open source, but source available and free of cost if you choose to build it yourself.)
- snvzz 7mo ago>aseprite grafx2 provides a decent alternative
- pessimizer 7mo agoGIMP is annoying/difficult to learn well, just like Photoshop is. Correction: GIMP is annoying/difficult to learn well, but not nearly as bad as Photoshop because it is organized logically and isn't burdened with sacred historical cruft, advertisements and product tie-ins. The difference is that once you learn Photoshop it is a skill you can use at many jobs, and GIMP is not. Using this post as an excuse to rant, I've always thought that GIMP's priorities should be to be usable for print (mainly color management, which I think is almost totally fixed and becoming smooth) and to improve compatibility between it and vector drawing software (like Illustrator/Inkscape[0]), and layout software (like InDesign/Scribus[1].)[2] If you're a European government or an individual rich person and you are really serious about software independence from the US, or if you're China/Russia/etc. and we know you're serious about it, you should throw about 50M at the problem. I think it would threaten Adobe so much that the US might lob a missile at you. ----- [0] Inkscape also hated print, and the possibility of real exact colors and real exact measurements, and basically prioritized web icons and art. They also have a UI that requires a ton of memorization of hotkeys (which was part of the motivation for creating the software in the first place.) They seem to have wised up and made serious improvements in all of those areas. [1] The only problem that Scribus has is a clunky UI that requires a lot of unnecessary clicks, which makes me suspect that it has deeper architectural problems. I think very few people work on it. It's ideally positioned, in the age of all books being online data, to create/become the future typesetting standard for people who want definitive versions of books rather than flowy ebook things which are not a significant improvement over .txt files. You could take a classic book and encode its typesetting, and rather than having 10M of blurry page scans combined with OCR info, you could just have 500K of text, fonts and typesetting information. With this, you could professionally print a perfect copy of the book, and as it looked when it was printed originally. [2] Inkscape and Scribus, in turn, should be concentrating on pdf compatability, and also a way to sneak into print shops would be to write a good FOSS imposer (https://en.wikipedia.org/wiki/Imposition https://en.wikipedia.org/wiki/Imposition) that integrated well with Inkscape/Scribus.