Sobotka: Why GIMP is inadequate
Posted Jan 11, 2011 13:58 UTC (Tue) by boudewijn
In reply to: Sobotka: Why GIMP is inadequate
Parent article: Sobotka: Why GIMP is inadequate
Well, all three main points -- 16 bit rgb, linear light rgb and performance with large brushes -- are all well known, and the first one even does have a bug report (https://bugzilla.gnome.org/show_bug.cgi?id=74224) and that big brushes are slow is reported as well (https://bugzilla.gnome.org/show_bug.cgi?id=304798, though I guess that also the painting itself should be faster according to the original author).
And nobody is denying that these are problems: the first two problems are supposed to go away once gegl gets properly integrated, and Alexia Death is doing extremely cool things with the painting engine in Gimp -- as well as willing to integrate gimp-painter patches.
But what you mean, I guess, is "Nobody should talk about problems and deficiencies in an open source application without filing the bugs and proving that to me!" And that seems to me unfair.
Not that I think that this guy has hit the nail on the head -- he seems completely unaware that there's actually work going on in all areas, he mentions Krita's decision to focus on painting, being unaware that it was Gimp's interaction design maintainer Peter Sikking who helped us reach that decision, just as he previously helped the Gimp team make the decision to go for high-end image manipulation.
Gimp hasn't reached that goal yet, and I guess it'll take a long time, but the team knows what they want and they have a plan to reach their goal. More power to them! They are doing some things right: a rigorous focus on stability (with to me, as Krita developer, enviable results), an interaction design maintainer who really watches over the interaction design (also with enviable results), a large support community in forums and a fame that attracts capable graphics coders for special features and experiments. But it takes time to reach a goal once you've set yourself one.
(I think there are problems in the gimp development, but those aren't mentioned in this article: gimp is extremely hard to contribute to because the codebase is huge (10 times as big as Krita), all in C, with a very strict coding style, not very modularized, not very well documented, with a development team that's not exactly known for welcoming newcomers.
Also, Alexia Death seems to me to be right if she says that what Gimp needs now is a dedicated GTK hacker, because GTK is so broken (https://lists.xcf.berkeley.edu/lists/gimp-developer/2011-January/026012.html) that they cannot implement many of Peter Sikking's design because GTK won't allow it.
to post comments)