Wow. I could've sworn Krita was only around 6 years old. I've only very recently started hearing about it.
There seems to be a phenomena I observe in the FOSS community where we reflexively respond to suggestions despite them being far beneath their FOSS alternatives. Only after digging or running into issues, do you find the good stuff. Brand name -> Low quality, highly mentioned -> High quality, rarely mentioned Photoshop-> GIMP -> Krita Windows -> Debian-family/Ubuntu/Mint -> Fedora I almost feel like a religious Zealo…
25 Years of Krita
31–40 of 101 posts
Re: 25 Years of Krita
#32Re: 25 Years of Krita
#33Earlier quoted context omitted.
There seems to be a phenomena I observe in the FOSS community where we reflexively respond to suggestions despite them being far beneath their FOSS alternatives. Only after digging or running into issues, do you find the good stuff. Brand name -> Low quality, highly mentioned -> High quality, rarely mentioned Photoshop-> GIMP -> Krita Windows -> Debian-family/Ubuntu/Mint -> Fedora I almost feel like a religious Zealo…
How is Fedora better than Debian? (genuinely curious)
Re: 25 Years of Krita
#34Re: 25 Years of Krita
#35Krita is a great replacement for photoshop.
Re: 25 Years of Krita
#36Sounds like developing in QT is awful. They have had to do so much work porting it to new versions of QT.
That's just any big framework. Porting a large codebase between major releases of GTK (or Javascript frameworks) isn't much better.
Qt5 was released in 2012. All of my LCL/Lazarus projects from that time open in modern straight-out-of-git Lazarus just fine. I'm pretty sure 99.9% of my LCL/Lazarus projects from 2005 (when Qt4 was released) also work out of the box, with the exception of those that tried to use strings as byte buffers (fixing this is a quick search and replace) since the datatype changed (this was a compiler/language change though, not a framework one). Retaining backwards compatibility is very important for LCL/Lazarus.
That said Qt has been better than other frameworks when it comes to backwards compatibility, after all you can use the Qt5 docs for Qt6 code and vice versa and things work 95% of the time. Actually i was working on some Krita plugin recently and i only had the Qt6 docs around but i never encountered any issue with what i was using.
AFAICT Krita's issue is mainly on the lower end of things and how they integrate with their custom OpenGL code.
Re: 25 Years of Krita
#37Re: 25 Years of Krita
#38Wow. I could've sworn Krita was only around 6 years old. I've only very recently started hearing about it.
There seems to be a phenomena I observe in the FOSS community where we reflexively respond to suggestions despite them being far beneath their FOSS alternatives. Only after digging or running into issues, do you find the good stuff. Brand name -> Low quality, highly mentioned -> High quality, rarely mentioned Photoshop-> GIMP -> Krita Windows -> Debian-family/Ubuntu/Mint -> Fedora I almost feel like a religious Zealo…
Re: 25 Years of Krita
#39Krita is a great replacement for photoshop.
No it is not.
Krita was meant to be an OSS alternative to Corel (ex Fractal Design, ex Meta Creations) Painter [1].
And that's what it became, eventually. And quite a bit more.
I've been using Photoshop and Krita since the first version of both of these DCC apps came out (and Painter too, btw). Professionally. I.e. for most of my adult life.
Krita is a great paint app. It's not a Photoshop alternative.
Photoshop is a great image manipulation app. It's not a Krita alternative.
Krita absolutely is a Painter alternative.
Painter is no longer a Krita alternative, if you need certain features (that's a topic for an entire blog post).
Re: 25 Years of Krita
#40Sounds like developing in QT is awful. They have had to do so much work porting it to new versions of QT.
That's just any big framework. Porting a large codebase between major releases of GTK (or Javascript frameworks) isn't much better.
MFC is slightly better, and MFC sucks (at least on MSVC 6.0 era)
WxWidgets was one of the best/easiest OSS ones.
The best library hands down was the one used by Borland C++ Builder (Windows only), VCL.
QT felt like going around in circles and a bit like those "useless superpower" charts, GTK like nobody had invented C++ yet.