[–] 1 point 1 year ago* (last edited 1 year ago)

CMYK support is getting there but very slowly.

You can import, export, and proof in CMYK today and you can have a CMYK color profile. GIMP 3.1.2 added total ink coverage for CMYK so 3.2 will have that. However, everything is still handled as sRGB internally.

With GIMP 3, all the required plumbing is there to handle CYMK natively. If I had to guess, I would expect it around GIMP 3.4. So, probably 5 years or more from now.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago

    GIMP follows the old Linux kernel versioning scheme.

    The second number is even for stable releases and odd for development releases. Given the frequency, you should think of the second number as major releases in the way you are thinking.

    GIMP was on version 2.10 for 7 years before the release of 3.0 and on version 2.8 for 6 years before that.

    A bump in the third number for GIMP really is a minor release with the second number (when even) signalling a major release. GIMP 3.2 will be the next “major” release.

    The first number changes very infrequently. It was 21 years between GIMP 2 and GIMP 3. I do not think we have any idea what the criteria will be to move to GIMP 4.

  • source
  • parent
  • context
  • [–] 3 points 1 year ago (3 children)

    More useful than that comment for sure.

    There was lots of useful stuff in this release. It is not like it just fixed a couple of bugs. More than enough new functionality to be newsworthy and enough for me to go get the new release for Mac (which does not auto-update).

    It is also great to track the incremental progress towards things like full CMYK support.

    You may also misunderstand how GIMP releases work. Things will probably move faster now that version 3 is out but there will be LOTS of progress in the 3.0 releases before they release 3.2. If you wait for 3.2, you will be waiting a while and miss many useful features. The 3.1.x series is a dev branch for more invasive changes. A lot of the nee functionality will appear in 3.0.x.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (1 child)

    it would be better for everyone if we could all be a little bit nicer

    I agree with that

    personal attacks

    I agree, personal attacks are bad

    “this code does not make any sense to me”

    But here is the problem. Your two versions are not the same. The problem is not that Linus does not understand the code. The issue is that he does.

    I believe strongly that high performance culture requires that it be absolutely ok to talk about the quality of an idea or about the work and that this NOT be seen as attacking the person.

    “You are an idiot” is not ok. “This code is garbage” has to be (at least from the guy whose job it is to determine code quality). You can say “this code is very low quality” or “this code is totally unacceptable” if you like.

    Co-pilots will allow pilots crash planes out of respect. Engineers allow bad designs to crash planes too. Neither of these are preferable to speaking openly and plainly, at least not in my view.

    Lives absolutely depend on the Linux kernel. It is ridiculous to say they do not. What do we value more, comfort or safety?

    Please be nice. Please also say exactly what you mean. At work at least. Suffering fools gladly is a better strategy at play and at home.

  • source
  • parent
  • context
  • [–] 3 points 1 year ago (3 children)

    To each his own.

    Personally, I would want to live in a house where someone loudly reacts to somebody suggesting to remove a load-bearing wall for cosmetic reasons. I do not want them to pretend that it is a reasonable suggestion. Speak plainly!

  • source
  • parent
  • context
  • [–] 1 point 1 year ago

    The last time I looked at this, it did not really add up. The “lack of supoort” was more for BIOS boot than anything. When they say “Linux”, they mean their ancient implementation of it.

    It would be a real shame if Linux lost foothold in its own country out of ignorance and bias.

  • source
  • view more: ‹ prev next ›