Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GIMP receives a $100K donation

gimp.org

Post reply on HN
Print view View original

251–260 of 318 posts

Re: GIMP receives a $100K donation

#251

Post by prokoudine »

_carl_jung wrote: post #68
nothis wrote: post #58

Earlier quoted context omitted.

3 months of a professional UI designer could easily quadruple the usefulness of GIMP for me. The UI, in its current state (I always use this disclaimer and it never changed in like 10 years), is a horrible mess and makes GIMP unusable for most professional work. There is no trend of it getting better. They need to hire someone from the outside, accepting that kick in the butt.

Overhauling the GIMP UI would take way longer than three months of a single UI designer. As an operation, we are talking UI/UX design, implementation, testing, and not to mention having to refactor existing code such that it can actually handle such a radical UI change. I'd put the (very fuzzy) estimate at something like 2 years of consistent (full time) effort from a team of, say, 5 people. That puts the cost of suc…

Yay, at least someone gets it :)

Re: GIMP receives a $100K donation

#252

Post by antt »

RussianCow wrote: post #225
geoah wrote: post #218

Earlier quoted context omitted.

Why not?

Because I would expect that you generally sacrifice part of your salary for the ability to work on free and open source software full-time, much like you would generally take a pay cut working at a non-profit.

If you're doing brain dead admin work sure.

If you're doing a contract not for profits pay the same as everyone else.

Re: GIMP receives a $100K donation

#253

Post by prokoudine »

yunyu wrote: post #158
rootlocus wrote: post #92

Earlier quoted context omitted.

Keep hoping, because the GIMP team "will use the money to do much overdue hardware upgrade for the core team members and organize the next hackfest to bring the team together, as well as sponsor the next instance of Libre Graphics Meeting."

Introducing usability and functionality improvements isn't mutually exclusive from doing those. At the very least, I'd expect some improvements to come out of the hackfest.

The last time (winter 2017) we did a hackfest outside of Libre Graphics Meeting, we introduced a bunch of improvements to layers' blending and compositing, improved color management, improved the PSD loader/exporter, improved menu structure, introduced painting on transparent layers in modes other than Normal (which is _huge_ for painters), and introduced Flatpak builds.

Re: GIMP receives a $100K donation

#254

Post by tracker1 »

gnulinux wrote: post #242
purerandomness wrote: post #222

Earlier quoted context omitted.

Your definition of "save" is not the common, user-centric one. As a user, I think about "saving" as a process to persist my work. If there might be technical fine-grained issues, show me a warning sign in the save dialog, but don't come up with a process that "makes me think".

> As a user, I think about "saving" as a process to persist my work. PNG is just a compressed pixel-to-colorspace format. It does not and cannot contain most of the information in your work. When you save a .png you're basically doing something similar to compiling C to machine language. You permanently lost all the high level information, possibly in a way you cannot track back (in the case of .JPG). This is not sav…

"Export As" vs "Save As" ... Almost any program that can "export" to multiple formats uses "Save As" for the display. This is just one example. And while I appreciate the nuanced nature, and frankly in this case could go either way. When you combine all the options/features Gimp is by far the hardest image ui I've used.

My favorite was probably PaintShop Pro before 10, and second is probably Paint.Net (if it had a few more features). A simple, easy to use interface with the majority of features really accessible. Gimp offers so much more, though frankly, it's about 10x as hard to use. I only do so when I want to do something that's difficult in Paint.Net or Krita.

I want to like it, I want to use it... that said, If you had a few users who like other software use it, nobody I know would choose Gimp over other tools as a preference. I don't always like changes that are made to an application I've used for a while, and can understand resistance from Gimp developers and users. It doesn't matter, sometimes convention should win, sometimes making things easier means change, and sometimes making things consistent means an inferior technical choice.

Re: GIMP receives a $100K donation

#257

Post by prokoudine »

Scene_Cast2 wrote: post #129
enriquto wrote: post #47

Earlier quoted context omitted.

What is exactly the problem with gimp's UI? I find it intuitive and very easy to use (but then, I have not used many other interactive imaging programs). Is it missing something important? Has too many useless features? GIMP's UI is alright for me, what I need are more features that are sorely lacking: 1) ability to work with images having an arbitrary number of spectral bands 2) floating-point pixel values 3) comple…

GIMP's IWarp workflow is horrendous. And this is saying something - photoshop's liquify could be much better too.

> GIMP's IWarp workflow is horrendous.

Welcome to 2018 where GIMP 2.10 is available and features the Warp Transform tool that does the same (actually, more) and works directly on the canvas.

Re: GIMP receives a $100K donation

#258

Post by prokoudine »

TekMol wrote: post #136

Please give us non-destructive adjustment layers! Please! Been waiting for this for years. On every new Gimp release I look through the new features and ... no. No adjustment layers. I'm confused how this is not the #1 priority. It has been what I am missing for years and years. And every time I talk to someone about Gimp vs Photoshop, they ask me 'Do you still have to cope with destructive adjustment curves and filt…

> On every new Gimp release I look through the new features and ... no. No adjustment layers.

While the roadmap has been stating for years that it's planned for v3.2 :)

> I'm confused how this is not the #1 priority.

Before 2.10 the top priority was completing the switch to the new image processing backend that makes non-destructive editing possible.

For 3.0 the top priority is switching to a newer, actually maintained version of the UI toolkit.

For 3.2 the top priority is, at last, the non-destructive editing.

It all makes sense.

Re: GIMP receives a $100K donation

#259

Post by prokoudine »

themodelplumber wrote: post #192
boudewijnrempt wrote: post #175

Earlier quoted context omitted.

So... I've had to read this about eight times, and two or three of those together with someone to figure this out... But what you're saying is "gimp developers work on gimp because they like gimp, while blender developers work on blender to see what people can do with it -- so they will not be able to spend this money effectively." -- or am I still misunderstanding you?

(Of course it would be Boudewijn Rempt)--much respect to you and thank you for your question. > gimp developers work on gimp because they like gimp I'd say: GIMP has always been good enough for GIMP developers as its own world to explore--what is it, what can we make it become for the sake of GIMP. I remember the good old days (frankly I'm not sure if this still happens) when a mailing list suggestion like "look, Pho…

> The latter type of focus, the internal focus, asks "what do _we_ want to do, what interests _us_ as a team, what's next for _us_" and I believe that's always been a feature of GIMP's existence

Right now, the focus is on completing the GTK+3 port for v3.0 and making room in API for upcoming serious changes in v3.2 such as non-destructive editing. Sounds good enough? :)

Re: GIMP receives a $100K donation

#260

Post by komali2 »

RussianCow wrote: post #187
komali2 wrote: post #177

Earlier quoted context omitted.

Wait, library management is supposed to be the main value prop? I didn't get the point of libraries - I already have my images in separate folders, what does the library actually add to that dynamic? Different folder, different instance of lightroom works for me.

Being able to organize thousands of photos dynamically by tags, date, etc, is enormously productive, as opposed to only having a single, static hierarchy through which to find photos. For instance, I could quickly retrieve all scenic photos across our entire collection.

Did not even realize tagging existed... but does that mean all photos must be in the same library? For example my workflow is usually

Pull pictures off camera manually into a date-named folder

Open lightroom, click "new catalog"

Put catalog into named date folder

Import those photos (import without move option)

Work on those photos, use the slider catalog thing at the bottom to filter by flagged (the ones I edited and like), then ctrl+a and export.

Post reply on HN