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."
As powerful as GIMP is, I find myself struggling to complete tasks that would be easier in Photoshop. More frustrating, however, is having to compile my own plugins. I still have not managed to compile one successfully (and I've been working with Linux since Red Hat 7.3).
The difference between spam and poop is that you don't have to dig through septic tanks looking for real food. -- Me
(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.
Then...Photoshop is a SDI application on the Mac. SDI vs MDI is hardly the reason professionals will not switch to The GIMP.
Like the article mentions, it's all about colour management and plugins. The former could be solved with code, but the latter is very much chicken/egg; third-parties won't write GIMP plugins until companies start using it, and companies won't start using it until their plugins are available.
Not to mention all the licensing fun of releasing closed plugins for a GPL application. That'd be fun...
I want to work in my RAW photos in 16-bit as much as possible before converting to 8bpp at the final step. GIMP doesn't do that, so I am forced to use photoshop.
>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...
People (like me!) complained for years that Photoshop only existed on the Mac and PC, and so, finally, Adobe ported version 3.0 (at apparently great expense) to the SGI. Unfortunately, it was a monumental failure -- Adobe sold perhaps hundreds of copies.
The sad thing about this is that now there is almost no way that Adobe would consider doing anything like that again, with Linux. They've been burned before.
It's a shame. I'm sure that they'd sell many more than a few hundred copies to the Linux market. Maybe even a thousand.
Hardware is so cheap these days, though, that you might as well have a Mac or Windows PC around to run Photoshop when you need it. After all, the software is going to cost you $1,000 or so, you can spring for another kilobuck on some hardware -- or you can dual-boot your Linux box under Windows.
As much as I'd like Photoshop to run under Linux for my visual effects company, in the end I would prefer that Adobe just make better versions that run under the toy operating systems. My painters will be happier that way, anyway.
Thad Beier
I love Mondays. On a Monday, anything is possible.
I do. I'm a professional, not a hobbyist, and want to do my damn work, not fuck around with the interface.
The Gimp is good enough for most of us. It is different than Photoshop so people need to relearn how to do some basic things which can painful for the easily frustrated. A better GUI for Gimp wouldn't hurt and I think they addressing some of the issues in 2.4. Also others have mentioned GimpShop, I'm not sure how mature that is though. But yes Gimp as it stands is not good enough for photo professionals because it lacks color management and built in CMYK support, even though a plugin exists. But then again how many photo professionals use Linux in the first place?
On a side note I'm really impressed with how much work/research Novell is putting into the Linux desktop. Instead the gradual long-term effort Red Hat has invested, Novell seems to be thinking short-term. Novell desktop 10 looks really interesting and their sponsorship of XGL is also really great. I'm glad someone is stepping it up.
The best education consists in immunizing people against systematic attempts at education. - Paul Feyerabend
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.
I'm sure there are plenty of developers that simply want Dreamweaver etc. who are quite capable of coding a standards compliant web page by hand. Nowhere in my original post did I say or imply otherwise. That doesn't take away the fact that a large number of web developers are completely lost without their tools. I've done a ton of web development for major corporations (mainly server side programming not the HTML/CSS) and I've worked with a ton of them. I also have many contacts who are web developers and the good ones always get a kick out of how many so called professionals in the industry are completely lost without their tools.
"A Lisp programmer knows the value of everything, but the cost of nothing." - Alan Perlis
The very fact that this question has to be asked says a lot about why Linux (and other OSS) has trouble making it in fields with established software. I presume that the people who wrote GIMP wrote it to meet their own needs, because they certainly haven't taken the time and effort to meet the needs of print graphics professionals. Even if you ignore the interface and a number of other shortcomings, the lack of CMYK support makes it IMPOSSIBLE for it to be used in a graphic arts environment for printed products.
The primary colors of light (and therefore monitors) are red, green and blue (RGB). The primary colors of printing are cyan, magenta, yellow and black (CMYK). A digital image starts out as an RGB and is edited that way, but it must be converted to CMYK before it can be sent to an imagesetter for four-color printing. This isn't a "good thing to have." This is a showstopper not to have. It's like having a car without wheels.
I keep hearing OSS people breezily dismiss criticisms of software such as GIMP or just insist that it IS good enough for professionals. The very fact that some people are arogant enough to try to shove tools onto people that WILL NOT DO THE JOB shows why it's hard to adopt Linux on the desktop. Linux has done well in areas where geeks have written software for other people like themselves. It has not done well in areas where the geeks don't "get" what professionals in other areas must have. A commercial company has a serious incentive to make software that fits the needs of those other people. The people who write OSS tend to just want to write things that are fun and useful to them -- and that severly limits adoption of Linux in non-technical areas. Of course, it also doesn't help that so many Linux people seem to take the attitude that the Linux desktop is fine, but artists and other non-technical types are just too stupid to use it.
David
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
One of the main reasons people don't care about GIMP, isn't just the questionably poor usability. It's still the features. Last time I check, things such as the ability to group layers, advanced typographical control, adjustable object effects, and color modes, were still far behind Photoshop.
Even in photography, I still find the GIMP lacking. The lack of LAB mode, which I often use, is one example.
The GIMP is a good project, and it sure has it's uses, but it's still far away from a Photoshop replacment for many people. It's like saying that MySQL is a suitable replacment for Oracles's top-of-the-line DB. For some; sure, for others; no F'n way.
The annoying thing about the colour depth issues is that there IS a version of GIMP that supports large colour depths - there is an entire fork of the GIMP tree called 'FilmGIMP' - and then, later: 'CinePaint' that's been developed with really comprehensive deep colour support.
The problem is at the core of the GIMP developer team's culture. If you hang out on the GIMP mailing list for any amount of time, you'll find it's an unbelievably hostile list. The members of the team seem to hate each other with a passion! There is constant bickering and any questions that are even a shade off-topic (or even on-topic but in the mailing list archives) will be flamed mercilessly.
It is that innate hostility that drove a wedge between the GIMP team and the consortium of movie art teams that put together FilmGIMP/CinePaint. That the project had to be forked in order to get such a basic feature done is just criminal.
GIMP is great - yes - but it could have been so much greater. It's amazing that it's done as well as it has.
www.sjbaker.org
For dealing with photos or even scanned images you will often want more than 8bpp, especially when you want to do things like shadow enhancement or highlight recovery. In this way it lets you choose what will be thrown away instead of having the camera throw information away when it converts to JPEG. There is a lot of detail that is often thrown away that can be brought out with the right software.
For example, one technique used when shooting photos in high contrast lighting conditions is to shoot the photos a bit underexposed then go back and adjust them after the fact, since otherwise the camera can screw up the highlights, often causing them to shift colors due to saturation. Having the extra bits gives a lot more room to change the photo later.
RAW images are becoming increasingly popular, and though there are several different formats, just supporting Canon and Nikon will probably make 90% of the people happy. For those not familiar with raw image formats, most high-end cameras support more than 8 bits per pixel, often 12 bits and preserve the original CCD/CMOS mosaic pattern. Code like dcraw has already been written which can read most of the formats out there. I myself as a Linux user have fallen in love with Bibble, which allows me to quickly go through hundreds or even thousands of photos and fix things like white balance, shadow recovery, lens distortion, sharpening, etc. all while supporting the higher color depth.
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
*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.
I'm a pretty advanced Photoshop user - I use it for both print and digital purposes and I've been doing so for over 10 years now. I like Linux and I'd really like to be able to switch to a Linux desktop completely one day. That said I'm giving GIMP a try every once in a while. People say it rocks once you clear the Photoshop mist and once you get familiar with the somewhat weird GUI you'll find it, well, awesome.
My conclusion so far is that while GIMP has a Photoshop resembling toolset it's really not a Photoshop competitor. Really. While Photoshop is overkill for John Doe, especially regarding the price (yeah, most people pirate it, I know), GIMP is quite sufficient. It's an awesome tool for removing red eyes in photos, fixing resolutions, brightness/contrast and stuff like that - but it's not competing with Photoshop. It's obviously not made for print due to the lack of CMYK-support, and for web production.. well, compare Photoshops "Save for web"-module vs GIMP's "Select a JPEG compression percentage please"-prompt.
I've seen work by one or two people who do some seriously impressing stuff with GIMP - and that's it. Those two people also seem to have been involved in the GIMP project since the dawn of mankind, might be a good indicator on how much time you need to spend before being able to use it fluently enough.
Some people who doesn't work with graphics professionally (or claim GIMPs awesomeness without even using it) will probably disagree with me and claim that I'm wrong. But hey, at least I've TRIED to use it. It's just completely pointless for me to even spend time with it when I have access to a (legal) Photoshop license. I don't think the GIMP project is useless though, as I said - it's good enough for the average guy, even though I think the UI could improve tremendeously.
www.freshpilot.com
As powerful as GIMP is, I find myself struggling to complete tasks that would be easier in Photoshop.
You mean stuff like resizing the brush with a keypress? After reading the manual, going to google, setting any arcanely named binding that might be it in the shortcuts preferences, the Gimp just sits there and stares stubbornly at me when I try it. Do these people never paint anything? OTOH, this is the same people that think that CTRL-K is much more logical for deleteing stuff than say, oh, I don't know... delete, maybe?
Apart from that, a lot of why the Gimp is such a struggle to use is those right click menus and image menus that the Gimp people are so proud of because they can do anything. Sure, they can do anything - but it also lists *everything*, always! It's called a context menu, and it could be incredibly powerful if it had any context. Oh, and things sorted in real categories.
I could very well live without a Photoshop interface, but I want a human interface.
Spine World
It's obviously not made for print due to the lack of CMYK-support
It seems that Adobe and their patents play a role in that, but its true of course that this is a serious limitation for those whoms work is going to be used in print.
and for web production.. well, compare Photoshops "Save for web"-module vs GIMP's "Select a JPEG compression percentage please"-prompt.
If you are doing graphics work professionally, is it too much to ask that you have some idea about how different compression levels work out? This is pretty equivalent to knowing how different kinds of paper work out when you profession is printing.
I am not a graphics artist, but I do run some websites that are used by graphics artists for publication. I had to tell each of them to stop using the bloody 'save for web' module for their pictures because the result of it is crap. Rather, they should be using jpegs in 1280x1024 resolution or better, compressed at 90% quality or better. The website will do recompression when needed. Of course the recompression by the website is why you should feed it high quality sources, but the 'save for web' confuses the hell out of those graphics artists exactly because it explicitly hides what it is doing from the user.
A simple example which bugged me this weekend. I needed extra space to draw in so I resized the canvas. But I can't actually paint there! Why? Because the canvas size changed but the layer size didn't. This is so stupid. I only had one layer, so why didn't it ask me if I wanted to resize the layer too, or even provide that as a persistent checkbox preference in the Canvas size dialog? GIMP is replete with stupid little things like this. Such as the foreground / background colour selector where it is entirely non obvious how it works with the same tooltip covering 4 distinct actions. Or the scale selection (as far as it works in Win32) does not support proportional scaling and the grabber behaviour is totally insane.
Rather than attempting to play the same complex notes as Photoshop (another lousy experience IMHO), perhaps they should be simplifying its day to day use first. Make the next version a usability & bug fixing release only. People wouldn't be pining so much for Photoshop or any other decent tool if the one which ships with Linux didn't make them want to gnaw their own arm off with frustration.
Novells conclusion from the survay
Don't fight for your country, if your country does not fight for you.
No, it comes down to the fact that the vast majority of graphic designers and artists don't work in a vacuum. Artwork gets sent to customers for approval. It gets sent to publishers and print shops for production. Those people have to be able to read those files with no hassle. They have to maintain color accuracy. They have to work.
If you're billing clients top dollar, and have print runs on the line that can easily cost hundreds of thousands of dollars, then risking that account just to keep from spending $600 on a professional-grade, industry-standard tool is... well... stupid.
Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
They just don't realize it and don't really have (as you said) the time to put into it. Which is still a failing of society.
Oh come on!, a lot of people do not *have* the time just because they DO NOT CARE!. They prefer playing with their Playstation, getting drunk or fixing their car than to get into the computer.
You fail to see that, at the same way you (and I) enjoy hacking the computer, normally people enjoy hacking their cars, stereo system or any other hobby they have. And it does not mean that the society is failing.
We all have our priorities, and although for you, the computer could be a very important tool, there is people who only use it as a comunication tool. Think as the telephone, you do not care how your telephone work... you may not care how is it programmed, you just want to pick up the phone, press the buttons and speak.
We all have our priorities, and the fact that the priorities of other people are not the same as yours does not mean their are doing any wrong.
Although I arrived late to the article, let me state something. This last week, I have been working in some simulations. I made a simulation on the computer wich gave me as results something like 400,00 MB in numbers.
Now, I needed to do statistical analysis on those things, unfortunately, the deadline of the paper is for this wednesday, and I have never used any of those Statistical analysis tools. I didnt need anything too fancy, only std. deviation and averages.
Guess what I used, Excel, it has an OK statistical analysis package. Now, I wont "rant" about the absence of that on OpenOffice, I did everything I needed in MS Office, but to do that I had to import my text files (delimited by a space) to Excel. I did some simple C programs to process my code and then just imported with the File/Open function of excel, it detected it was text file and a wizzard guided me through the import stages.
Now, what does all of this have to do with the "linux still not ready"?, well, after finishing, I thought "how could I do it with OpenOffice" because you know, everybody says OpenOffice is as good as Ms Office (something I do not believe). Well, I tried to open one of those files with the File/Open IN OpenCalc and it just opened a OpenWrite window with the numbers HA!
I looked for an "Import" button, I tried with the "Document Import wizzard" without luck. So I could not even *start* to compare it.
Now there are a number of several details that I *doubt* OpenCalc has, that Excel does besides importing a file or being able to make cross references between worksheets and books but, you must see that the devil of the commercial vs open software is (as in everything else) in the DETAILS. Those small details that people take from granted when using Photoshop, Excel, Word, etc. And the fact that in some of those products you can go from 0 to a complete work in a few minutes (God, this is the first time I do a *real* statistics analysis).
Ubuntu is an African word meaning 'I can't configure Debian'
If you are a freelance web designer, you "must" know the subtile differences between CSS rendering on Firefox and on Internet Explorer. You shouldn't be afraid to open notepad and write the HTML code directly. You must know all the little tricks. If you don't then you are doomed.
But...When you work inside a web agency, then roles are defined. The web designer concentrates on...design. He/she makes the lay-out according to the corporate identity, the marketing stuffs, ergonomy, and so on. His/her role is purely on design. There is another guy, a technician guy who knows everything about techniques. He/she will transform his/her work into a working HTML based lay-out.
He will give all the guarantees that it will work on all major browsers.
Then a web developer will put the lay-out inside the CMS, or as the user interface on a custom built web application.
This is a team.
On large scale project, you've got enough work justify a full-time job on design and another one to make the result HTML compliant.
My company, a small web agency outsources everything related to design. We use traditionnal infographists. We had to "educate" them on basic stuffs, but it in the end, it helps us to concentrate ourselves on the web site features and technical parts.
Most technicians are extremely bad at communication/graphism and so on. Most of us can't understand why we should spend hours to make a stupid paragraph aligned with some tiny parts of the lay-out, nor can we understand that the customer may get mad because font is Arial 10 instead of Arial 12 on the subtitle. We simply can't understand why it matters so much and why the customers cannot understand the beauty of our new CMS with all the new features that let us make multilingual content with simple clicks or this new XML import feature that works automatically with one of their partners.
A lot of talended designer are bad on the technician part. They simply don't care about how it works.
Sorry mate, I use UNIX every day, to run really big serious programs costing tens of thousands of dollars per year in licensing. I do it from the GUI. Sure, I occasionally type in real hard to understand commands like 'mdi', or 'dtfile' into the command line, but mostly it is just me and that big old boring HP UNIX GUI. The longest batch file I've ever written has 3 lines.
Elitism such as yours is both misplaced and counter productive. There is no really hard reason why a Knoppix type system, and a bit of fine tuning, would not make a consumer level OS. The problem is not the underlying OS, the problem is at the GUI level, and as such is solvable by scripting at the VB level.
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.
Mmmh, no. You underestimate the stupidity of the average user.
We are talking about people who can't install a program in Windows, who can't guess that if you want to open a file you might want to check "file" menu.
I've seen people using Word to copy files (open & save as) and centering lines using spaces completely ignoring align icons.
What you forget is that User Interfaces are designed to make interaction easy while car engines are not.
Using your analogy an average user wouldn't know how to change gears or which pedal is the brake.
Krita, the painting and image editing application for KOffice is probably a better alternative to Adobe Photoshop on the Linux desktop. It is nicely integrated in KDE and its codebase is cleaner than that of GIMP, so it is easier to add features at a fast rate. In fact, even GNOME devs have been amazed by how fast it's growing.
Well, while you are technically correct, you shoot past the who point by miles.
The idea isn't to try to actually view at that color depth. Its already beyond the capabilities of many video output devices, and even possibly the human eye. But again, thats not the point nor in dispute.
The issue is the accumulated filter effects and tranformations applied to a digital image. Each such effect can create subtle artifacts and degradations. When you start with 8bit/color channel (traditional 24bpp) then these can build up fast to become noticably visible in the final image.
But if you apply those effects to a 16bit/color channel (48bpp) image, the artifacts don't become noticable as quickly, if at all, assuming you are using a good quality image manipulation program. Then when all is done, you can convert your final image to 8bit/channel (24bpp) such as jpeg and have a clean image.