GIMP 3.0 has been more than one decade in the making as the port from GTK2 to GTK3, also transitioning away from Python 2 to Python 3 support, and a wealth of other improvements from the UI to lower down into enhancing this open-source Photoshop alternative.

The GIMP project announced on X/Twitter today that they have entered the string freeze for this much anticipated release.

top 50 comments

sorted by: hot top controversial new old
[–] 93 points 2 years ago (2 children)

Just in time!

Preparing for GTK 5

(Trying to be funny here, don't downvote too much!)

  • source
  • hideshow 4 child comments
  • [–] 88 points 2 years ago (3 children)

    okay I'll bite, what does "string freeze" mean here?

  • source
  • hideshow 6 child comments
  • [–] 46 points 2 years ago

    Fuck yeah! Go GIMP! Also announced on Mastodon fwiw:

    https://floss.social/@GIMP/112995553132226800

    I'm super excited about 3.0 🪇

  • source
  • [–] 44 points 2 years ago (2 children)

    Place your bets, are we getting GIMP 3 before 2025?

  • source
  • hideshow 4 child comments
  • [–] 42 points 2 years ago (4 children)

    port from GTK2 to GTK3

    Migrating from an already rooten toolkit to a toolkit that is dead since a few years.

    Nice.

  • source
  • hideshow 7 child comments
  • load more comments (1 reply)
    [–] 38 points 2 years ago (15 children)

    can they unfreeze the name?

  • source
  • hideshow 17 child comments
  • [–] 46 points 2 years ago* (last edited 2 years ago) (7 children)

    I know people like it, but I agree.

    And as silly as it sounds, I think the name is a big part of why businesses haven't ever wanted to touch the project or invest in it.

    Imagine telling your average upper management guy or board member that you want your workers to use software called gimp. They're probably not gonna want to hear you out.

    Anecdotally I know of a local NHS practice that refused to use GIMP, and was even sceptical of other subsequent suggestions of other FOSS due to the terrible impression they got from the GIMP name during a pitch to use more FOSS.

    I get it's their identity, their project. Nobody has the right to dictate the name but them. But it's also fair to point out that they probably shot themselves in the foot by giving their software a juvenile and weirdly fetishy name.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 28 points 2 years ago (1 child)

    Why doesn't someone just fork it and change the name?

    Like, I dunno, "Super Human Image Treatment" or "Consistently Lovely Image Treatment Oriented for Real Imaging Stars"

  • source
  • parent
  • hideshow 2 child comments
  • [–] 32 points 2 years ago* (1 child)

    Actually, someone did, changing the name to "Glimpse". They announced it as an explicit fork that would continue development under the new name.

    As far as I know, that's as far as they got.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (5 replies)
  • [–] 11 points 2 years ago (1 child)

    They won't. It's an old topic and they are clear about not changing the name. Anyone having a problem can fork and rename the project. But it seems not to be a big issue that nobody wants to do it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (2 children)

    I believe that there is a project that aims to do just this but I can't remember its name.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 13 points 2 years ago

    If you can't remember the name, it was probably not a good rename. "Glimpse" was the name, as the other user noted. ;-) On a more serious note, I actually liked the name Glimpse. But they did more than just renaming the project. They had plans to make it very different from Gimp too. So it probably died because of being too ambitious.

  • source
  • parent
  • load more comments (1 reply)
  • load more comments (13 replies)
    [–] 34 points 2 years ago

    I just flipped through the introduction of a GIMP book that the authors hoped 3.0 would be out so they could cover it but ultimately based the book on 2.6 due to delays. It's copyright 2012, apparently something (didn't) happen.

  • source
  • [–] 31 points 2 years ago

    No better default gui?

  • source
  • [–] 28 points 2 years ago

    we really got kde 6 before gimp 3

  • source
  • [–] 19 points 2 years ago (2 children)

    Isn't this the version where they pinky promised there will be CMYK support?

    <ducks, runs>

  • source
  • hideshow 4 child comments
  • [–] 15 points 2 years ago (1 child)

    From https://developer.gimp.org/core/roadmap/ for GIMP 3.0:

    Space invasion (work in progress):

    Various color management improvements, CMYK support (not as core image format, but import/export and picking/choosing/viewing)…

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago

    That's the one! Didn't bother finding the source myself, thanks for going the extra bit kind stranger!

    Looking forward to eventually burying the old "sticking with Adobe because GIMP doesn't support CMYK" argument.

  • source
  • parent
  • [–] 14 points 2 years ago (1 child)

    Will there be a big party where we can be baked

  • source
  • hideshow 2 child comments
  • [–] 7 points 2 years ago* (last edited 2 years ago) (1 child)
    load more comments (1 reply)
    [–] 4 points 2 years ago

    hope gimp becomes better yeah ik it is not liked that much

  • source
  • load more comments
    view more: next ›