News for hackers. Stuff that matters.
Re:GIMP – 2016 in review by coldtea on Tuesday January 17, 2017 @04:46AM (#13416206)
>Even though I hear this quote ringing in my ear, and I can't seem to shake it, mainly because of who said it

1) Photoshop had a 10+ year head start and tons of patents.

2) Adobe can pay programmers to work on it as their main and sole focus. GIMP is stuffed by volunteers.

3) Adobe can pay programmers to work on boring parts. OSS programmers tend to navigate to the "glorious" and "fun" parts.

4) Adobe has extensive testing equipment and top notch relations with top designers using its products for feedback.

5) At some point GTK, the toolkit GIMP (and Gnome and tons of other stuff) is based on, had just one developer working actively on it. I know because he blogged about it, and was fed up. That's not really what you want for your core infrastructure.

6) Adobe actively maintains Windows and OS X releases. GTK has mostly given up on other platforms and had historically had lots of problems.

Re:GIMP – 2016 in review by nothis on Tuesday January 17, 2017 @11:16AM (#13418714)
GTK is probably the main reason Gimp isn't a serious competitor in professional work, then. I can imagine what monumental task it must be to maintain a cross-platform GUI toolkit, but it's IMO the single most important aspect of Gimp. Let's face it, all the features are there. Maybe 5% of Photoshop's deep ocean of features is actually used by the average user, Gimp can provide almost the complete functionality. Some extra performance and nice-to-have tweaks might still make a difference, but they're not what's holding people back from considering a free option over a several-hundred-dollar one. The user interface is what's crap. Sorry, GTK, it just is. Copy-pasting what I wrote a few months ago:

>Out of curiosity, I tried installing Gimp to see how much has changed (for the better?) since I last checked it out. The tool interface doesn't quite fit into its window by default so you have a tiny little scrollbar at the bottom that you have to scroll to see the full text. I resized it. After popping out a submenu, it once again didn't fit.

This is plain unacceptable. Yes, this is 99% there, it's a minor thing, it's probably thousands of man-hours to avoid a gazillion other bugs and issues and even get to this point. But it's not enough. A UI for such a tool, where you actually fiddle with it a lot, has to be perfect. Perfect on a technical level, perfect in a Apple-y "let's ensure that the empirically determined most-used features are shown first and less-used stuff doesn't clutter precious screen-space" sense that takes long and frustrating trial-and-error involving real-world feedback. You can't have a button that's 15 pixel larger than it has to be. You can't have a layout arrangement that wastes half a window because it's poorly aligned. You can't have spacing that's inconsistent enough to make you hesitate clicking an icon because you're not sure if it's connected to some other element of the interface.

Open source/free software needs a user interface push, but apparently that's not a sexy field to work on.

Re:GIMP – 2016 in review by prokoudine on Tuesday January 17, 2017 @03:20PM (#13420797)
> Let's face it, all the features are there.

You really should prepare for a ton of bricks about to crush you down as people discover that you think adjustment layers, layer effects, or CMYK support is "5% of Photoshop's deep ocean of features" :)

Re:GIMP – 2016 in review by klodolph on Tuesday January 17, 2017 @05:34PM (#13422109)
16-bit, Lab, good text support…
Re:GIMP – 2016 in review by gurkendoktor on Tuesday January 17, 2017 @10:58PM (#13423850)
> GTK is probably the main reason Gimp isn't a serious competitor in professional work, then.

Xamarin Studio is built using Gtk and actually looks nice on macOS, or at least I have seldom heard people complain about it:

https://blog.xamarin.com/the-making-of-xamarin-studio/

I think the problem is that Gimp is understaffed to produce a Photoshop killer with any toolkit.

Re:GIMP – 2016 in review by flukus on Tuesday January 17, 2017 @11:04PM (#13423868)
There probably aren't that many xamarin studio users on mac and most of them would be developers anyway. If something looks out of place, developers are often oblivious to it (how long would it take you to spot a font out of place?) but artists are hyper-sensitive to it.
Re:GIMP – 2016 in review by gurkendoktor on Wednesday January 18, 2017 @10:18PM (#13432680)
Photoshop, Illustrator, Lightroom, and non-Adobe tools like Affinity Designer all use portable, non-native UI code. That hasn't stopped artists from using them. I don't out-of-place UI is the reason why people avoid Gimp.
Re:GIMP – 2016 in review by sebnukem2 on Tuesday January 17, 2017 @09:07AM (#13417587)
GTK literally means the Gimp ToolKit. It's not based on, it's the toolkit that started it all.
Re:GIMP – 2016 in review by digi_owl on Tuesday January 17, 2017 @06:15AM (#13416570)
> 3) Adobe can pay programmers to work on boring parts. OSS programmers tend to navigate to the "glorious" and "fun" parts.

Aka CADT...

Re:GIMP – 2016 in review by yjftsjthsd-h on Tuesday January 17, 2017 @06:32AM (#13416645)
Yes, but it's harder to judge volunteers who are only working at all because they enjoy doing so.