Slashdot Mirror


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."

23 of 819 comments (clear)

  1. GUI perhaps? by Anonymous Coward · · Score: 5, Insightful

    (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.

    1. Re:GUI perhaps? by slashdotnickname · · Score: 5, Insightful

      Also the name sucks. At best its confusing, at worst its offensive.

      How's it offensive?

      I was born with a left club foot. Fortunately, it was braced and reset before I can remember. Even though I've always walked with a slight (almost unoticeable) limp, I've never considered myself inferior in any way. The word gimp has never crossed my mind as being offensive. What I find offensive though, is when people try to tell me that I should be offended by. Gimp (in one of its definitions) is just a descriptive word for someone with a limp, so I'm a gimp, big fricking deal...

    2. Re:GUI perhaps? by TekPolitik · · Score: 5, Insightful
      The right-click-on-photo part that brings up every command?

      That sucks. It should only bring up stuff relevant to manipulating bits of the image. The right-click menu is also known as the context menu - if I'm right-clicking on pixels I want something that relates to pixels. Some things that definitely should not be there: File, View, Image, and then most of the things on the sub-menus (which are also arranged in terms of GIMP internals rather than in terms of user-oriented categories).

      The pull down menu above the photo that brings up every command?

      It's not so much the menu as the fact that everything is impossible to find in the menu because it was apparently arranged by a seriously deranged individual bent on avoiding natural categories. Even when you can find something it takes 3-4 non-obvious menu options in sequence to do something that is one menu option in other drawing software. The floating toolbox that brings up every command?

      The customizable tab box which permits instant access to your most important subset of commands?

      Sensible defaults are better than telling people to customise what is out of the box the Worst... Interface... Ever.

      That near every subset of commands can be 'torn off' as a floating toolbar?

      What the hell does this have to do with anything? Actually, now that I think of it, it does have something to do with the problem since these floating toolbars don't - they sink right to bloody bottom of the window stack and you have to go hunting for the bastards (this doesn't happen in an MDI interface by the way).

      Or the part that doesn't look like Photoshop's unique boxes-in-boxes interface, a GUI style last universally popular in the Windows 3.x days?

      And yet a style that is retained in every serious image editor*... but nooo, the GIMP people are right and everybody else is wrong.

      GIMP's user interface really is a festering pile of crap. Go ahead, GIMP-fans, do your worst to my karma - I have plenty.

      * Yes I know GIMP doesn't have it. I meant what I said.

    3. Re:GUI perhaps? by Imsdal · · Score: 5, Insightful
      It seems to me that if it hasn't been changed in six years then it's not that great of a problem for most users.

      Oh My God. Oh My God.

      That is the single least insightful thing I have ever read at /.. Could there possibly be another reason for things not changing? If Microsoft has kept something crummy for six years, would it be reasonable for you to state that it's not a problem for most users, and thus nothing to complain about?

      My suggestion to all the people bitching about how GIMP sucks (...) is to become a part of the community.

      This is so typical of what is wrong with the open source movement. In real life (which was what TFA was about) most people can't afford to "become part of the community" because they have real, actual work to do. I use at least ten applications on a very regular basis. I most certainly can't afford to "be part of the community" for all of those. In the real world, what counts is how well stuff actually works right now, not how good they could possibly become in the future if everybody would just help out. Sorry, but that's the way it is.

      I think it's a little unseemly to bash people who give you something for free.

      TFA is about why people don't use the free stuff. That makes this comment a bit disingenious, don't you think?

      It doesn't make sense to be oblivious to real user needs and, simultaneously, to bash real users for not using specific stuff. I know I'm Captain Obvious for spelling this out, but it seems to be needed.

    4. Re:GUI perhaps? by Imsdal · · Score: 5, Insightful
      If you're pissed off (...)

      Well, I'm not pissed off, but I am disappointed.

      First of all, for the record it should be noted that I never use either GIMP or PS. I'm talking about the open source community and their attitudes in general. I do feel very strongly that the thoughts dicussed in the post I replied to applies to most, if not all, free software projects. That's my opinion, not a verifiable fact. If you differ, fine, but please be aware that just having a different opinion won't make me use alternative software. Nor will it convince many others.

      Closed source companies in general, and Microsoft in particular, are incredibly much better at building applications that are usable for regular, professional users. By professional I mean users who use the software for work and who, accordingly, are prepared to pay for the service of using the software. I do not mean "super power users".

      Too many people in the open source community dismisses these people as morons or worse. That's fine, I suppose. It's not like the "morons" care on way or the other. The problem is that a lot of pepople really want to affect lasting change, making users switch from MS to free stuff. And if one wants that, that attitude simply won't cut it.

      This thread explains why perfectly clearly, but too many people here refuses to acknowledge that. To me, that is disappointing, because it means that Excel will continue to be better than the alternatives. So will SQL Server, Visio and Photoshop. It doesn't *have* to be that way, because usability isn't that difficult. But it requires a completely different mindset than what is currently prevailing.

      Finally, good usability requires huge amounts of humility. Isn't it ironic (in the English sense of the word) that in this particular case Microsoft has that humility, whereas the open source community lacks it?

  2. Huh? by Otter · · Score: 5, Insightful

    >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.

  3. Re:They have a point... by Anonymous Coward · · Score: 5, Insightful
    Being that there is a UNIX version of Photoshop (OS X) it should not be too difficult to wrap the inners with an X GUI outers.

    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.

  4. Re:What about.... by ctishman · · Score: 4, Insightful

    I do. I'm a professional, not a hobbyist, and want to do my damn work, not fuck around with the interface.

  5. Gimp would get a lot more popular if... by foxwitt · · Score: 5, Insightful

    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.
    1. Re:Gimp would get a lot more popular if... by Radak · · Score: 4, Insightful

      If Adobe figured out some way to lock down Photoshop so that it couldn't be pirated as commonly as it is currently.

      Does Adobe even really care? Most everyone who uses Photoshop professionally pays for it (and it's obviously priced for that market). Photoshop probably owes some of its ubiquity in the professional graphics world to its wide availability for piracy.

      The fact that pirated Photoshop lives on millions of personal computers owned by people who honestly would never pay the price Adobe is asking for it (mine included, I admit) is costing Adobe very little revenue while giving them huge amounts of exposure, which amounts to free advertising.

      For the sake of their stockholders, they publicly mind, but I think the lack of any real attempt to prevent its piracy speaks a lot to how they truly feel about it.

  6. Perfect example of OSS problems by DavidinAla · · Score: 4, Insightful

    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

    1. Re:Perfect example of OSS problems by DavidinAla · · Score: 4, Insightful

      You don't have a clue what spamming is, do you?

      You also don't seem to understand real-world workflow in printing, at least based on the ludicrous suggestion that a job be sent to a printing company and let the printing company do all of the conversion. A normal printing company expects you to be bright enough to convert your own RGBs to CMYKs. If you want them converting RGBs for you, they're going to charge you extra for this useless work on their part. I've dealt with at least a dozen printing companies with lots of jobs over the last 15 years. If you can regularly send clean files that are ready to be sent to an imagesetter with minimal prep, you're going to get a better price on your work.

      If you think lack of CMYK support isn't enough to keep GIMP from being used by people in the printing industry, you're either ignorant or just too stubborn to see that GIMP isn't ready to replace Photoshop in the real world. I honestly don't know which it is.

      David

  7. Underrated point by tyler_larson · · Score: 5, Insightful
    First of all, Photoshop -- on either Mac OS X or Windows -- is the default photographic and prepress program for serious graphics firms.... Photoshop is simply "The" application that professionals use.

    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
  8. Re:They have a point... by complete+loony · · Score: 5, Insightful

    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.
  9. Re:How can we take this seriously... by Theatetus · · Score: 5, Insightful
    Bluefish is sort of a programmer's editor with extra features for HTML, not a web site design tool like Dreamweaver. The user shouldn't have to look at HTML source much, if at all.

    *blink*

    A web designer shouldn't have to look at HTML source much?

    --
    All's true that is mistrusted
  10. Re:How can we take this seriously... by Jekler · · Score: 5, Insightful

    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.

  11. Re:They have a point... by dido · · Score: 5, Insightful

    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.
  12. Re:How can we take this seriously... by SillyNickName4me · · Score: 4, Insightful

    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.

  13. Re:How can we take this seriously... by shmlco · · Score: 4, Insightful
    "It comes odwn to laziness i guess."

    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.
  14. Re:How can we take this seriously... by xtracto · · Score: 4, Insightful

    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'
  15. Re:How can we take this seriously... by oliderid · · Score: 4, Insightful

    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.

  16. Re:How can we take this seriously... by theCAS · · Score: 4, Insightful

    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.

  17. Re:16bpp voodoo, show me specs. by gorim · · Score: 4, Insightful

    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.