Live data from Hacker News

GIMP development - What’s the point?

mail.gnome.org

21–30 of 149 posts

Re: GIMP development - What’s the point?

#21
post #18
post #14

Earlier quoted context omitted.

Is there a way to add decent CMYK support to GIMP? Is it technically unfeasible, or is it something the main devs are simply uninterested in?

http://www.gimp.org/docs/userfaq.html#i-do-a-lot-of-desktop-... there is however some cmyk support currently if you need it: https://wiki.archlinux.org/index.php/GIMP/CMYK_support

Thanks for the link! So it's low priority for the existing devs (and I understand the reasons why... they make a lot of sense, actually!), but they are open to new devs helping with this. I assume it would be no small feat.

Re: GIMP development - What’s the point?

#23
I appreciate GIMP for what it is, and use it on the occasion that I can't quickly do what i need with ImageMagick or pixlr. But I'd gladly pay for Photoshop and other Adobe tools if they compiled natively on linux.

One problem with the characterization implied in [a,b] is that it ignores the impossibility of opening a file correctly and completely that was originally compiled in a tool that's been the industry standard for well beyond my own years (I got started on Photoshop 4 in 1996 - the first Windows release, and before then, Paint Shop Pro).

Literally not a single designer I've worked with in the last 15 years as a professional has ever even considered using GIMP (most don't know it exists). So if they want to send me their "source", it's in a PSD. And said source is going to be huge with layer effects / cropping / transitions, and all sorts of advanced Photoshop-specific things applied.

And I'll open that file in GIMP - I try at least once a year - and it will show maybe 5-10% of the layers and will look nothing like the original. And then I'll fire up Windows in a VM and actually get work done.

As for starting my own projects in GIMP, I fall squarely into group "a", and I feel no shame for it.

    a) User has tried GIMP, but didn't take time to learn enough to get past things that aren't obvious.

    b) User has heard that GIMP is hard to use, and is not an adequate tool for professionals.

Re: GIMP development - What’s the point?

#24
post #12

What's the point? It's a helpful question for narrowing your focus, but at the end of the day, there isn't always one, and it needn't be a lofty philosophical goal. Did the MDL team need a point to develop Zork? Did Thompson need a business reason to write UNIX? Did the AI lab ever justify extending TECO far beyond its original intent, into the first version of EMACS? Sometimes, although not all the time, "because I…

"Because I can" is of course a valid reason, but having a better goal is more motivating, especially if it's a team instead of a single person. I believe GIMP does have a better goal than "just because", and in my mind it is achieving it. I'm not a graphics designer and therefore I have the luxury of not being locked-in with Photoshop's advanced features; therefore all my image manipulations are done using GIMP, Krit…

Oh, of course. It's just that I don't think that "what's the point?" is as significant a question as many believe it is.

Re: GIMP development - What’s the point?

#25
Before reading that email, I had a different thought about the title "GIMP development, what's the point?" In a time before touchscreen mobile devices and apps came into the picture, people who were somewhat serious about image editing would use GIMP or a pirated copy of Photoshop. There were also a few other applications, free and paid, with a much more limited set of features (but have improved over time).

With touchscreen devices and apps, image editing, or rather, photo editing, has become more about using different apps for different specific use cases, and using filters and other "preset" tweaks along with additional adjustments if at all necessary. This is nowhere close to the power that GIMP offers for someone who knows how to use it and what can be done with it. But it is adequate for most people and is easy to use. In this respect, the title question could become more widespread as people hear less about GIMP.

After reading the mail and the comments here, another thing that occurred to me about the title is that projects like GIMP, LibreOffice, etc., (and even Linux, GNOME, KDE, etc.) show themselves as phenomenal highlights of what truly free and open source software can be and serve as a great inspiration for others to embark on such really complex and multi-decade work in other areas. A GIMP developer is contributing to much more than GIMP alone if you look at side effects. It's a world that couldn't have been imagined several decades ago.

I believe the developers who have contributed to these projects and continue to do so should be extremely proud of their commitment to FLOSS and the amount of work they have put in. Yes, some FLOSS applications may have deficiencies in features, stability, performance and other areas (which many commercial applications do too). But questioning the dedication of developers or asking for the justification of efforts spent by developers who're working with the FLOSS principles is completely missing the point in the overall scheme of things, and worse, missing the benefits enjoyed by and made available to humankind as a whole.

Re: GIMP development - What’s the point?

#26
post #23

I appreciate GIMP for what it is, and use it on the occasion that I can't quickly do what i need with ImageMagick or pixlr. But I'd gladly pay for Photoshop and other Adobe tools if they compiled natively on linux. One problem with the characterization implied in [a,b] is that it ignores the impossibility of opening a file correctly and completely that was originally compiled in a tool that's been the industry standa…

You blame GIMP for not opening PSDs correctly, but note that it's not an open format and it's not a standard. GIMP developers can do nothing but try to reverse engineer support for it.

Re: GIMP development - What’s the point?

#27
I haven't used a direct image editor in a very long time and I don't think I'm missing anything.

Digital Fusion is free. Houdini Indie is $200. Nuke is available for linux. These are all node based work flows that don't destroy anything. You don't have to undo because you create a graph of operations without changing your source directly. They aren't useful for painting directly with a tablet, but anything else they do very well at.

Re: GIMP development - What’s the point?

#28
post #23

I appreciate GIMP for what it is, and use it on the occasion that I can't quickly do what i need with ImageMagick or pixlr. But I'd gladly pay for Photoshop and other Adobe tools if they compiled natively on linux. One problem with the characterization implied in [a,b] is that it ignores the impossibility of opening a file correctly and completely that was originally compiled in a tool that's been the industry standa…

You blame GIMP for not opening PSDs correctly, but note that it's not an open format and it's not a standard. GIMP developers can do nothing but try to reverse engineer support for it.

You're absolutely right. The bar I'm setting is probably too high, but it's not set from anything beyond my desire to get work done. Literally: "nothing personal, but I can't use this"

Re: GIMP development - What’s the point?

#29
post #23

I appreciate GIMP for what it is, and use it on the occasion that I can't quickly do what i need with ImageMagick or pixlr. But I'd gladly pay for Photoshop and other Adobe tools if they compiled natively on linux. One problem with the characterization implied in [a,b] is that it ignores the impossibility of opening a file correctly and completely that was originally compiled in a tool that's been the industry standa…

You blame GIMP for not opening PSDs correctly, but note that it's not an open format and it's not a standard. GIMP developers can do nothing but try to reverse engineer support for it.

PSD is not an open format but it is most definitely an industry standard, and being unable to support it properly makes GIMP an inferior replacement for professional graphics work because of that.

Re: GIMP development - What’s the point?

#30
post #4

Stories about an eloquent, suave believer enlightening a misguided, clearly-in-the-wrong naysayer may sometimes be true, but never very convincing. > In this case, I opted to give the fireworks/show. My weapons of choice this time included the unified transform tool, the handle-transform tool, and the warp transform tool Which prompts the leering, misinformed troglodyte to consider the error of his ways, to "imagine…

I tend to agree with you. GIMP is a very important project in my view because it provides legal, cross-platform access to a baseline of image manipulation tools. The above-and-beyond feature set is fantastic, but not the reason why I love it. I suppose this isn't directly related, but following the theme of OSS alternatives to commercial software... after being ignorant of the OSS desktop application world for a few…

Natron and Godot have been added to my bookmarks.

Thank you for sharing, my good man. I will playing with them later to see how the next generation of OSS desktop apps have improved.

Post reply on HN