“Why are you trying to run Photoshop on Linux? Just use GIMP.” This suggestion never held much weight, and today, it holds even less.
A few years ago, I had a Twitter spat with someone involved in the GIMP project, the GNU Image Manipulation Program, often touted as the “open-source Photoshop alternative.” I argued that GIMP had fallen significantly behind and was not a viable option for professional visual and graphic designers. This view, based on my personal experiences, highlighted the shortcomings that prevent GIMP from being a reliable tool in the professional design world.
The discussion started when I contrasted Photoshop and GIMP’s features, specifically smart objects. In non-destructive editing, smart objects are crucial. Another designer chimed in, noting that smart objects are industry standard and are found even in free web-based Photoshop alternatives. However, the GIMP team member claimed this feature was on their roadmap and shared a link. Upon reviewing the roadmap, I realized there was a disconnect between GIMP’s development priorities and the needs of professional designers.
The roadmap featured several planned non-destructive editing features, but they quickly fell flat. The “linked layers” feature was their solution to smart objects, but it was far from the same. Not only could smart objects not be imported into GIMP from .psd files, but the entire user experience was cumbersome. Instead of nesting non-destructive layers within your working file, GIMP would “link” external files as layers. Despite professional designers voicing their concerns about this implementation, the developers persisted with their approach. One user, Steve Hardy, referred to smart objects as the essential feature that elevates Photoshop above the competition and described GIMP’s linked layers as a more complicated solution.
Reflecting on my early career, I owe a lot to GIMP. It was a valuable tool in my formative years as a designer. However, the project seems to be stagnating, mainly because the developers are not seeking feedback from professionals who use design tools daily. This insular approach makes me question the project’s overall goals and direction.
Despite its shortcomings, GIMP still has its place. It offers features that Photoshop doesn’t, like importing and exporting developer-friendly formats and better control over exporting GIF animations. However, its role in professional workflows is limited.
Meanwhile, commercial products from Adobe, Affinity, and Figma are gaining more compatibility on Linux through WINE, Proton, and web-based solutions. These options are often expensive, users would prefer an open and native alternative to both these and GIMP — something like PhotoPea, which showcases what a modern tool can achieve with the right focus and development. Created by a single developer, PhotoPea offers Photoshop features, including smart objects, and runs on a modern tech stack. This raises the question: is technical debt one reason GIMP cannot catch up? Perhaps it’s time for a community-driven image manipulation program to emerge alongside GIMP.
The disconnect between designers and GIMP is widening, partially illustrated by how differently designers and developers think. I hope to be part of the solution by teaming up with other technically minded designers who share my hope for powerful, libre design tools. Until then, the community needs to understand that “just install GIMP” is no longer a solution for designers looking to ditch Windows for desktop Linux. Today, the relationship between Linux and designers remains strained, and GIMP’s current trajectory isn’t helping bridge this divide.
In summary, GIMP is outdated, struggling to catch up, and challenging to develop new features for. The developers’ resistance to input from professionals exacerbates the issue. The design community on Linux deserves better, and it’s high time for a modern alternative to emerge.
Links:
https://gitlab.gnome.org/GNOME/gimp/-/merge_requests/823
https://medium.com/@kevdoy/how-open-source-gave-me-my-start-in-design-f39c9086a64c
