Yesterday I posted here wondering about better-than-basic image editing for Mac OS X. Herewith a summary of the guidance I got, and a bit of boggling in the face of the OSS edifice.
Of these, the GIMP apparently has the best price-performance ratio. That's if you don't factor in the multiple hours of fetch-and-build time which is pretty well automated but is distracting and makes your computer run slow. More on this later.
I managed to get the Gimp running, and hoo-boy, let me tell ya this sucker does a lot of things. I'm pretty sure it does everything I could possibly want and then some.
But I'm not sure I'm going to be able to use it. The reason is, it's an X Window System (let's abbreviate that XWS) application, and the XWS-ness of it is really in your face:
I suspect if I were living in the Gnome or KDE environment, all this would feel perfectly smooth and natural and the barrier to entry would be much lower. So the question is, do I try to learn to love this thing or go get the Adobe product, which is kind of the standard?
(Several hours pass...)
At that point, someone came into the office and told me that the same blob graphic I'd had to take home to Paintshop had some miscolored anti-aliasing, and could I fix it. Not with Graphic Converter, but, I had a running Gimp, so I gritted my teeth and fired it up. There's no faster way to learn a package than having to use it to get some work done.
And... well, it's got some things going for it. The brushes and erasers and pencils and flood-fillers and flashlights all seem to be a little smarter than what I'm used to. You can switch back and forth between tools with keystrokes. I got the job done amazingly quick given that I didn't know the program.
But the save dialogue is really klunky, yes of course I want to export it to indexed format to save it, just do it, don't make me say yes. And then I wanted to do a flood-fill with a new colour that I'd cooked up and it just refused to do it; it would flood-fill only with white, even though it would pencil in my colour. I eventually found a workaround, but it was pretty baffling.
Open Source Bogglement · To install this thing on OS X, you open a terminal window and type:
sudo fink install gimp
Fink (the OS X Unix software package manager) thinks for a minute, and informs you that it's going to need to install 42 (!) other packages first. It takes several hours (on my 500MHz TiBook) to fetch, compile, and install all of these. It was trouble-free except for I had an out-of-date version of Apple's X11.
I was doing other work, but couldn't avoid glancing over from time to time at the endless screens-full of fetch/build/compile messages streaming past (see above for a sample).
After a couple of hours of this, my mind began to boggle a bit, as the
collective weight of the hundreds of contributors and thousands of
person-years began to sink in.
gnome, the XWS itself; and all these things living and growing.
The world of software development really has split into what a famous
Canadian once called “two solitudes.”
The other solitude may be read about
I guess this of course is the traditional cathedral-vs.-bazaar metaphor, but I like that metaphor less and less, the collective genius that underlies something like the Gimp is bigger than a hundred cathedrals and their surrounding bazaars, it feels more like a city, or a planet, under continuous construction.