Hacker News Reader

Comment by AlyssaRowan | Hacker News Reader

It's been how many years? And it's still 8-bit?

Maybe the GIMP needs a fork. I like it, but it's a bit crap.

That's what the CinePaint fork (originally Film Gimp) is, support for high-resolution, high-bit-depth images for "deep painting" of film assets.

Is CinePaint still under development? From the sourceforge site it seems as if it was abandoned. Also, CinePaint doesn't run on Windows, which in my case is a deal breaker...

The problem does not seem to be GIMP if I understand the article correct, but the GEGL code (or the developer of it) which it relies on.

GEGL and Gimp are pretty much joined at the hip. While they're in name separate projects, they're very much developed for one another.

GEGL is developed for GIMP, and other projects. http://www.jonnor.com/2014/04/imgflo-0-1-an-image-processing... http://www.jonnor.com/2014/11/imgflo-0-2-the-grid-launched/ Disclosure: I'm a GEGL dev and the imgflo maintainer.

The 'other projects' part is one of the reasons why the proposed solution 'just strip all colorspace info, assume it is the same throughout entire processing pipeline' is not acceptable for GEGL, even if that might somewhat close to the typical usecase for GIMP.

Around 20 years :) However, development version is 16bit,32bit,linear capable for around 2 years now.

Why is it that problems that are obviously due to lack of man-power in a project are more likely to cause people to call for forking the project into another one that also lacks man-power, instead of considering joining the development team to increase its man-power? The phenomenon fundamentally doesn't make sense to me.

> Maybe the GIMP needs a fork

Yeah, sure. All the new developers that the team is currently missing will just _materialize_ out of thin air.

Reply on news.ycombinator.com