Gimp source code is pretty old. Adding stuff like 16/32 bit support is not easy.
On other side Krita is newer, uses QT, is developing faster etc..
GIMP development - What’s the point?
41–50 of 149 posts
Re: GIMP development - What’s the point?
#42Sorry to say I don't think GIMP is the best example of a great FLOSS project.
Many other projects are very competitive (or better) than commercial options but GIMP is not even close.
They just released support for 16bit/32bit/c color last year which is needed for so many scenarios.
The unified transform tool mentioned as a highlight is really a pretty simple thing to code.
They are 5-10 years behind what you get in PS for $10/month. It's a killer for any professional have tools that far behind their peers.
The UX has always been poor and unnecessarily complicated. I resent the implication it's the user's fault for not taking time to learn. There are many examples of complex professional systems that prove a decent UX is still possible.
Re: GIMP development - What’s the point?
#43I am a Krita fan. It's taken the throne of all my graphics creation and modification needs.
https://krita.org/en/download/krita-desktop/
Re: GIMP development - What’s the point?
#44Sorry to say I don't think GIMP is the best example of a great FLOSS project. Many other projects are very competitive (or better) than commercial options but GIMP is not even close. They just released support for 16bit/32bit/c color last year which is needed for so many scenarios. The unified transform tool mentioned as a highlight is really a pretty simple thing to code. They are 5-10 years behind what you get in P…
Edit: [Deleted]
I'm sorry, but I don't find the tool intuitive. I ran into issues using it. I installed fresh copy and tried steps commenters suggested and it worked well. However this was not my experience a mere two days ago.
Re: GIMP development - What’s the point?
#45Sorry to say I don't think GIMP is the best example of a great FLOSS project. Many other projects are very competitive (or better) than commercial options but GIMP is not even close. They just released support for 16bit/32bit/c color last year which is needed for so many scenarios. The unified transform tool mentioned as a highlight is really a pretty simple thing to code. They are 5-10 years behind what you get in P…
> The UX has always been poor and unnecessarily complicated.
I'm afraid a lot of photoshop ease-of-use boils down to :
More tutorials are available for PS
Those who complain already have an existing investment in learning PS
I started using both at about the same time and I found PS more annoying except for one thing, -the multi window UI (which is now fixed).
Those
Re: GIMP development - What’s the point?
#46I would like to give another try of GIMP later today.
I remember the first time I tried GIMP. The user experience wasn't good. After knowing you had to double click a button to toggle it, I immediately dropped GIMP.
I also had bad experience with gdk as a developer. I remember it didn't have an installer on windows, and it needed so many dependencies. Getting all the required dlls was a huge pain. Whereas Qt is always nice and easy with good documents.
gdk didn't seem to have a native mac backend. It needs XQuartz, which I don't like. I don't want to install X windows on mac, doesn't make sense. The fact that gimp is under gnome worried me.
Doing image processing software is difficult, but making the ui of it should be relatively easier. GIMP might be strong at processing images, but its ui was really messed up I think.
But I will try again to see if there is any improvement.
Re: GIMP development - What’s the point?
#47gimp has handled all my image processing needs for a two? decade(s) and done it easily, thanks.
Re: GIMP development - What’s the point?
#48Sorry to say I don't think GIMP is the best example of a great FLOSS project. Many other projects are very competitive (or better) than commercial options but GIMP is not even close. They just released support for 16bit/32bit/c color last year which is needed for so many scenarios. The unified transform tool mentioned as a highlight is really a pretty simple thing to code. They are 5-10 years behind what you get in P…
Edit: [Deleted] I'm sorry, but I don't find the tool intuitive. I ran into issues using it. I installed fresh copy and tried steps commenters suggested and it worked well. However this was not my experience a mere two days ago.
?
I'm by no means a pro but I can crop an image using gimp in less than 2mins and that includes figuring out where the tools are (I only open it whenever I upload images I guess every third month.)
Re: GIMP development - What’s the point?
#49Sorry to say I don't think GIMP is the best example of a great FLOSS project. Many other projects are very competitive (or better) than commercial options but GIMP is not even close. They just released support for 16bit/32bit/c color last year which is needed for so many scenarios. The unified transform tool mentioned as a highlight is really a pretty simple thing to code. They are 5-10 years behind what you get in P…
Edit: [Deleted] I'm sorry, but I don't find the tool intuitive. I ran into issues using it. I installed fresh copy and tried steps commenters suggested and it worked well. However this was not my experience a mere two days ago.
Don't know what you're talking about? Cropping and scaling take one click and mouse drag or menu selection respectively.
Re: GIMP development - What’s the point?
#50I 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.
For the completeness, the famous "PSD is not a good format" rant: http://codepad.org/DidDsbjF (it is not available at Google Code anymore).
The reply from Adobe: http://blogs.adobe.com/jnack/2009/05/some_thoughts_about_the...
They both explain, why expecting 100% PSD compatibility is unrealistic.