HN

Comments (140)

• Menu

  Liftyee
  I don't get everyone's complaints about the interface. I've been using it for years, once you learn where things are I can get what I need done. The learning curve (finding where functions are, the right tools for each job, etc.) wasn't much different from other software like Blender or Darktable (or even Davinci Resolve).The panels concept might be the most intuitive part of it, but Blender also has different panels and modes. And the tools being combined into few buttons is similar to CAD programs I've used.Anyone enlighten me on actual usability problems (and not pedantry like "the spacing of these buttons is uneven"?) Perhaps I've gotten used to using unintuitive software.
• Menu

  lightwords
  You know what? The hate GIMP gets in the comments is entirely self-inflicted. Everyone praises Krita and Blender because their UIs are consistent and look good. GIMP, on the other hand, looks like a toddler worked on it: switches are huge compared to text, buttons and text have no padding and are squeezed together, and icons are oversized and scattered everywhere.People might say, "You can just join the project and fix it yourself." But the team and community actively resist change and sabotage efforts to make GIMP more mainstream.
• pinkmuffinere
  Autosave sounds nice, I’m excited to have that!I appreciate the backwards compatibility they highlight in the article, and more generally the ownership oss gives you over your files. My small business uses gimp, canva, and Inkscape, and they all have their purpose, but one of the complaints we have with canva is that it’s really hard to get the original files backed up somewhere, aside from canva itself. You have to download each file individually , which is quite a pain (please correct me if there’s an easier way!). Gimps openness is an obvious path for oss, but really is a great feature. If the gimp team stops, we’ll still be able to edit our gimp files. If the canva team stops, we mostly lose all the canva stuff.
• kvemkon
  Zipped XMLPreparation for the future XCF (24.09.2023)https://gitlab.gnome.org/GNOME/gimp/-/work_items/10076Someone proposed newer ser-/deserialization approaches, but this didn't result in a discussion.
• amelius
  They should make it easy to install and use GenAI plugins (without messing with GPU drivers, etc.)
• Menu

  mimasama
  Zipped XML? Isn't that just OpenRaster? (which is already supported by GIMP anyway, but also supported by Krita and other image editors)
• Menu

  dm319
  Non-destructive filter layers caught my eye, and has been something I've missed since moving off Windows/Photoshop to Linux. Looking around it seems like they introduced this in V3, which is great to see.
• Menu

  dvh
  I just installed Ubuntu 26.04 and it's gimp starts for 14 seconds.
• Menu

  bulgur999
  As usual, whenever GIMP is involved, all we get are negative, often unfounded comments about an excellent piece of free software that is massively used and developed with very limited resources, doing its job really well.There’s something so pleasant about having GIMP around, efficient and so far removed from the disgusting greed that drives so many of the projects featured here.
• Menu

  socalgal2
  Zipped XML. Welcome to 1999 designs
• Menu

  spider-mario
  > For instance, we’re quite proud that a XCF file made by a small company for their logo in 1998 still renders the same way in the latest version of GIMPHow do they pronounce “XCF” such that it’s “a XCF file” and not “an XCF file”? “Xeceff”?
• bobspoogeragi
  [dead]
• Menu

  mattkevan
  [flagged]
• AltruisticGapHN
  [flagged]
• Menu

  TiredOfLife
  I thought every developer of this moved to the Glimpse fork
• Menu

  roschdal
  Zipped XML sounds like a bad idea. It's slow and bad. I say XCF forever.