Writing a Gimp 3.0 Plugin

Original Article ↗ Hacker News Discussion ↗

GIMP 3.0 Expectations and Platform Shifts

  • Several commenters want GIMP to succeed as a way to leave Adobe, especially when moving from macOS to Linux.
  • macOS frustrations cited: poor SMB support, Mail.app behavior, weak default window/file management, and Apple’s broader ecosystem/politics.
  • Some users report that after finally “committing” to GIMP and understanding it, it’s good enough for serious photography workflows.

UX, Workflow, and Target Users

  • Persistent perception that GIMP is “by coders for coders,” not visual artists; others dispute this and blame open‑source incentives rather than intent.
  • UI is widely seen as clunky compared to Photoshop and Affinity, though some argue it’s just different muscle memory.
  • 3.0 is said to improve UI and add features like multi-layer selection and better layer boundary visualization, but one user found it less space-efficient and had tablet detection issues.
  • Tips: use the command palette, change icon themes and tool grouping, and customize keybindings (including Photoshop-like setups). A dedicated UX issue tracker exists.

Missing or Desired Features

  • CMYK and print workflows remain a major sticking point for professional designers; 3.0 RC has CMYK import/export and soft-proofing, with full CMYK mode on some developers’ to‑do lists.
  • Requests: simple shape/line tools without paths, Lightroom-style single-panel color correction, better vector/PDF editing, and InDesign-like layout tools.
  • Specific gaps mentioned: easy non-pixelated text scaling (unanswered), better multi-layer manipulation (partially addressed in 3.0), and resynthesizer plugin availability (now reportedly working on 3.0 RC).

Plugins and Embedded Python

  • Thread notes that GIMP embeds its own Python interpreter; several people praise this compared to tools that depend on system Python.
  • Comparisons with Inkscape, FreeCAD, KiCad, Blender show varying approaches to scripting and API stability; Inkscape’s extension model is criticized as fragile.

Alternative Tools

  • Affinity, Krita, Darktable, RawTherapee, Paint.NET/Pinta, and Photopea are frequently named as more pleasant or specialized alternatives depending on task (painting, RAW workflow, quick edits).

Name Controversy

  • Large subthread debates “GIMP” as an ableist and sexual slur versus a harmless acronym.
  • Some say the name alone blocks institutional/educational adoption; others (especially non‑native English speakers) see the software as the primary meaning and consider concerns overblown.
  • Past renaming attempts (e.g., forks) did not gain traction, which some cite as evidence that the name is not the main barrier.

Open Source Dynamics and Adoption

  • Tension between users’ complaints and “if you don’t like it, fork it” responses.
  • Some accuse GIMP’s culture of ignoring long‑standing UX/feature feedback; others defend slow volunteer-driven development and point out that GIMP is widely bundled and useful, especially for web work.
  • Debate over whether better UX and a different name could make GIMP an Adobe competitor, or whether industry standards and pace of development are the true constraints.