GIMP Not Enough for Linux Users?
nursegirl writes "Novell has been running a survey about apps that people need in order to convert their data centers or desktops to Linux. The online survey has been running since Jan 13, and Adobe Photoshop was at the top of the list as of February 1. Desktoplinux.com has an interesting article about why the existence of the GIMP isn't enough for many professionals."
(dons flame resistant suit of anonymity)
Maybe this is because GIMP has one of the most god-awful GUIs known to man. I mean seriously, it seems to be designed to hide functions and impede work, not t'other way round.
>99% of business desktops don't have Photoshop, let alone whatever a "datacenter" involves. If Photoshop is at the top of Novell's list, all it shows is that if you have an open web survey and ask Teh Community for responses, you get replies from 15-year-olds.
What I'm listening to now on Pandora...
I don't understand why people find this so impossible to understand -- the MacOS APIs (Carbon and Cocoa) do not exist on other platforms. You can can compile vanilla Unix applications on MacOS X, but you can't trivially recompile (or wrap) a Cocoa app on Linux.
If Adobe figured out some way to lock down Photoshop so that it couldn't be pirated as commonly as it is currently. I know tons of people who use Photoshop and praise it to the heavens, but not a single one of them actually put the money down on it. I work in a university environment, so there're lots of legal copies of Photoshop around, but a lot of people work with their own hardware, so many copies that get used for preparing images for publication aren't legitimate.
I use the GIMP for the same tasks, and get results that are just as good, though. I think that for most image processing, the GIMP does everything the average user needs it to do, and more. I'm not denying that it doesn't meet the needs of certain professionals. However, if people weren't able to get pirated copies of Photoshop readily, they'd find that the GIMP does the job they need it to do.
Today our lesson will be Chapter 1 of Elementary Necromancy: Proper Use of a Shovel.
This really is the key. GIMP will never have more than a marginal user base because they don't understand their users. Their users--nearly all of them--are Photoshop users (or potentially ex-Photoshop users).
Good user interface design means not just creating an inteface that "makes sense," it's also creating an interface that works the way the user expects it to work. If over 90% of your users are used to the way Photoshop does function X, then you sure as hell better implement function X the way Photoshop does. Not because that way is better or makes more sense, but because that's what the user expects you to do, and any deviation from those expections means your app is "broken" in their eyes.
Competing on features in this sort of market is futile. Your program may be able to give me the moon on a stick; but if I can't easily make it work, it might as well do nothing at all. The success stories--those projects that have managed to supplant a deeply-entrenched competitive offering--have always acknowledged this fact and have modified the behavior of their own product to compensate. The failures in this arena (GIMP being the most famous) always refuse to acknowledge the effect on their users' expectations caused by their competitor's dominance. For projects like the GIMP, it seems a matter of pride to not be influenced by such an unworthy competitor.
"With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea...."
RFC 1925
So perhaps someone should start a project similar to WINE, to add Carbon and Cocoa API compatibility.
09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
*blink*
A web designer shouldn't have to look at HTML source much?
All's true that is mistrusted
I must say, well said. I don't agree with much of it, but you make your point well. I think the failings are in Linux and OSS and not in society. People often better themselves, the problem is that time is a limited resource, and which topic they choose to better themselves with is frequently an exclusive option. Given a 4 hour time block, a typical artist might have a choice... they can dive into one of their projects, add shadows, retouch some photographs... or they can spend it learning a new application. Most people will choose to better themselves by refining their ability to do what they already do well. Maybe using the GIMP would be a marvelous idea that enables them to surpass their wildest creative dreams. But there's really no way to know that before doing it. A person is just as likely to spend hours a day for a few weeks learning a new program only to discover it doesn't offer some core functionality they already had in an existing program.
People aren't stupid. The elitests who believe the average user, and average person, is a gibbering idiot is usually just as dumb when they are confronted with tasks outside their element. A Linux guru might wonder why everyone else is just too dumb to use all the wonderful CLI tools and scripting capabilities, yet when confronted with an automechanical problem, the mechanic is chuckling to himself about how Mr. Linux Guru is too dumb to even perform basic maintenance on his own car.
Like I said, time is a limited resource. Everyone can't spend all their time being an expert at everything.
Well, for Cocoa anyway, there's GNUstep, as, if I'm not mistaken, it's an implementation of the OpenStep specification that was created for NeXT and is still used today for MacOS X as Cocoa. Once GNUstep is reasonably completed, it would in theory be possible to have a certain amount of source-compatibility between any platform with GNUstep and Cocoa. Carbon, now that's a different story...
Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.