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

819 comments

  1. How can we take this seriously... by iamlucky13 · · Score: 3, Insightful

    ...when the author suggests that Linux using webdevelopers need Dreamweaver to create sites?

    1. Re:How can we take this seriously... by baldass_newbie · · Score: 3, Insightful

      Boy, you're missing the point.
      This isn't about current 'Linux using webdevelopers', this is about folks who need certain tools to get things done.
      And this is ignoring folks who work in products that won't respond because they KNOW they'll never be built on Linux (.NET, Lotus Designer, Dreamweaver, etc.)

      Some shops require certain tools be used, like it or not. You want folks to be able to make a business case? Make certain that every app they'll need is ported.
      Don't offer half or 3/4 baked alternatives. Mac OS X is justthisclose, but still lacks certain toolsets.
      Linux isn't even in the fucking game.

      Look, I love the penguin. I feed the penguin. But don't put down folks WHO YOU NEED to cross over. Yes, some folks NEED these tools because of some PHB. Help them make the case. Don't act all 1337 because you can hand script some animation foo on GiMP.

      Idiot.

      --
      The opposite of progress is congress
    2. Re:How can we take this seriously... by ForumTroll · · Score: 1

      Because unfortunately there is an extremely large number of web developers that wouldn't have the slightest clue where to begin without Dreamweaver, Frontpage, Flash etc. Perhaps something like Bluefish would help them make the transition (I've never used it so I can't really offer much of an opinion there). For the small amount of HTML/CSS that I do I've always found jEdit to be quite nice and it's supported on multiple platforms.

      --
      "A Lisp programmer knows the value of everything, but the cost of nothing." - Alan Perlis
    3. Re:How can we take this seriously... by iamlucky13 · · Score: 1

      Well I was half-trying to joke, but apparently I either missed or you didn't read the article before typing out your response...

      I wasn't speaking to the business case for Linux, which I admit is shaky in a lot of areas. The thing that gets me is the suggestion that a Dreamweaver port is more of a holdback for Linux adoption than a Photoshop port is.

    4. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Because he suggests no such thing?

    5. Re:How can we take this seriously... by cgenman · · Score: 1

      what Windows-only applications, if ported to Linux, would increase the likelihood that people would switch to Linux

      It's not that Dreamweaver is necessary for making sites on linux. It would make it easier to transition between the two OS's for dreamweaver shops... which are most of 'em.

    6. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Perhaps there are a number of developers who also *want* Dreamweaver. Thought about that? It's not about whether or not developers can't edit code, I can code up an entire site in Notepad if I want to. But why the hell would I? Do you also suggest people don't use OpenOffice to edit their Word documents because they can't see the markup?

      For a small amount of pissy HTML/CSS coding, go crazy with jEdit and Bluefish. Until I can find something that gives me the flexibility that Dreamweaver does, why would I change? Same with Photoshop. I need these tools to do my job. I'm not going out of my way to use sub standard options and have to dick around all day just to prove some point the corporate world.

      If my job involved browsing the web and checking email all day, I'd be all Ubuntu'd up. But it doesn't so I'm not.

    7. Re:How can we take this seriously... by baldass_newbie · · Score: 1

      Oh, er, uh...he-he. Yeah. That IS funny.
      Gotta be careful on the dot. All that is typed in jest is not read in jest and all that.

      I just get fed up with the cavalier attitude that folks can pick whatever they want and then someone holds up a half-baked alternative. No, I don't mean GiMP, so hold the flamewars for other folks.

      Carry on.

      --
      The opposite of progress is congress
    8. Re:How can we take this seriously... by ForumTroll · · Score: 4, Informative

      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
    9. Re:How can we take this seriously... by larry+bagina · · Score: 1
      Did you read the article ("Why photoshop tops linux most wanted apps list")? Nobody suggested that Dreamweaver is more important than Photoshop. In the survey, Photoshop was #1, Dreamweaver was #3.

      For years, some linux/FOSS fanatics have insisted that GIMP is as good as photoshop, or even better. Survey says: No.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    10. Re:How can we take this seriously... by ubernostrum · · Score: 1, Interesting

      For a small amount of pissy HTML/CSS coding, go crazy with jEdit and Bluefish. Until I can find something that gives me the flexibility that Dreamweaver does, why would I change? Same with Photoshop. I need these tools to do my job. I'm not going out of my way to use sub standard options and have to dick around all day just to prove some point the corporate world.

      For a "small amount" of "pissy" coding? I make my living coding in Bluefish and Emacs, and nothing else; no WYSIWYG HTML/CSS editor comes anywhere near close to the clean, clear, semantic code I can produce by hand, so to me Dreamweaver and its ilk are seriously sub-standard options.

      If my job involved browsing the web and checking email all day, I'd be all Ubuntu'd up. But it doesn't so I'm not.

      I've been on Ubuntu for just shy of a year, and on various flavors of Linux exclusively for over five years now. I've yet to run into something I need to do, either for work or for entertainment, that I need any other OS for.

    11. Re:How can we take this seriously... by Animats · · Score: 1
      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.

      Actually, it's surprising that the open source community hasn't developed a really good web design tool. So much open source work revolves around web site design and implementation, yet there's nothing as good as Dreamweaver 4 in the open source world. (Dreamweaver took a wrong turn after v4; the "MX" versions are designed to make you overuse Macromedia technologies, especially Flash.)

    12. Re:How can we take this seriously... by xhrit · · Score: 1

      As an x-windows/new linux user(pun intended), I find using the gimp instead ov photoshop suits my web development needs. Dreamweaver I can not replace as easily.
      Dreamweaver contains the old cold fusion studio code. As far as I am aware there is no other client that can connect to cold fusions rds to transfer files. If I were to use another IDE or code by hand in a kedit instead ov dreamweaver developer mode, I would have to run ftp in addition to cold fusion server. More work, less security. not really an option. Instead, I get by w/ an old copy ov Dreamweaver MX and crossover wine.

    13. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Well done! Huzzah for you! There's about a brazilian developers out there using almost as many combinations of tools. The original topic here was what folks wanted to use on Linux. You don't want Dreamweaver? Too easy, you're sorted. I would want it. In fact after 3 months in my current employment I've had to switch from Ubuntu back to Windows, mostly related to bloody Flash building requirements. At the same time, I struggled to find something that let me work as efficiently as Dreamweaver does at the moment. That's probably got a lot do with habit and some things could have been overcome, but I do need accurate visual layout too. So all we're talking about here is personal preference. Rest assured I was in no way suggesting that those not using Dreamweaver are somehow building something of a lesser quality, in fact I think you'll find the general opinion out there is quite the opposite. Your assertion that Dreamweaver can't produce the clear, semantic code you can is also a little presumptive. You assume we're using Dreamweaver to 'produce' code and forget it is in fact a text editor. I can edit the markup as cleanly and easily as you. So to suggest it is sub-standard is wrong: some of it's users may be sub-standard and may rely on it's pre-built code but that's a different matter.

    14. Re:How can we take this seriously... by eno2001 · · Score: 3, Interesting

      But look at who they're surveying... These folks will NEVER use Linux no matter what. I'm a 24/7 Linux user myself and I know that for a fact. The main reason why is that with the possible exception of Apple's Mac OS X, Unix is not something that Joe and Jane Average can work with. The main reason being that if you want to do interesting things in Unix, you MUST be exposed to the shell and some form of scripting or (gasp!) programming. Sure, that works fine for me and a lot of other folks. And people like us can dumb a Linux distro down enough for grandma to use it. But, in doing that we also wind up having to support our creation. I know. I've done it. My wife and my parents (previously all computerphobes) are now Linux users. It is possible to make a Linux system easy enough for someone who knows nothing about computers to use. It's a lot harder to make Linux work for someone who actually has some inkling of what they want to do, but aren't quite at the level reqiured to just make it work with custom scripting/coding.

      I see GIMP in relation to Photoshop in the same way that the old Syntrillium CoolEdit (a Windows audio editor) was to Digidesign's ProTools. CoolEdit was arguably much more powerful in terms of features. It was also far more scientific with special filters that appealed to egg heads more than audio designers. But if you asked a ProTools fan to work with CoolEdit, they'd curl up and die. The main reason is that ProTools lack of abilities is what made it easy for them to use. In the same way, GIMP throws a lot more features/filters at the user than Photoshop in it's default configuration. Those extra features are confusing to people who are used to Photoshop. I made the transition from Photoshop to GIMP right around the time that PS 3.5 was out. I'd say that currently GIMP does everything that Photoshop 3.5 did and more. The UI took some getting used to, but once I was used to it, it did everything I needed. Still... that doesn't help people who don't want to have to get used to something. It's a sad truth simply because they could better themselves if they put the effort in, but most people simply don't want to.

      You know that if Photoshop or Dreamweaver were ported to Linux that people wouldn't leave their current platforms. There isn't much that Linux offers them immediately, so why would they do it? Again, another sad truth is that many people don't have enough of a long term view to see how much they'd save in both OS upgrade costs and hardware costs. Most folks aren't smart enough to realize that if they switched to Linux, they wouldn't have to pay for upgrades. However, more importantly, they don't realize that they could hold onto their machines a while longer because the newer versions of Linux rarely push you off of your current hardware onto the latest and greatest. I've got a box that will hit ten years old next year and it's running the latest apps I need (GIMP, Firefox, Thunderbird, OpenOffice, BIND, Wine, eDonkey2000, GAIM, GRdesktop, VNC, RealPlayer 10, Xine 1.x, MPlayer, Grip, Rio Karma Music Manager Lite, Icecast/Ices etc...). Not only that, but it's supporting five simultaneous users all doing similar things. I challenge anyone to take a nine year old Mac or Windows box and run the latest OS and apps on them. But this is something that most people don't even realize is possible. They've been conditioned to believe that they need new machines every couple of years. That'show bad it is in the computer industry right now. I don't see it getting any better either. As soon as people want to make money with this stuff they will stop at nothing to convince you you need to buy more stuff. In perpetuity.

      So, I don't expect to see the average person running Linux anytime soon. Anyone who does is being foolish. But this is not due to failings in the Linux distros, the core of open source itself, or even the GIMP project. It's due to the failing of our society to educate people enough to actually understand the tools they work with day in an

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    15. Re:How can we take this seriously... by wesw02 · · Score: 1

      Very Well Put. I wonder, do we share the same brain?

    16. 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
    17. Re:How can we take this seriously... by dbIII · · Score: 1
      For years, some linux/FOSS fanatics have insisted that GIMP is as good as photoshop, or even better
      When I first used gimp it had undo and photoshop didn't - so in my opinion and for the limited uses I put it to it was the vastly superior raster image editor. They are different programs with different advantages and expecting the GUI to be identical for both is really a bit strange. It's different - don't expect any visual memory of what path to move the mouse in photoshop menus to do you any good. Don't think of pushing buttons - think of what end result you want because the process will be different.
    18. 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.

    19. Re:How can we take this seriously... by glassjaw+rocks · · Score: 1

      Thank you. Please mod parent up.

      --
      -gjr
    20. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Im surprised at anyone that says 'Linux isn't even in the fucking game'. Despite what we may think about what app needs to be ported, is it really about only that ? Lets take this scenario - I went to DeVry and did just about every bit of homework in Linux ( programing, web-design, presentations, etc.) I had to learn different apps, but in the end every application worked. This is not just about most wanted apps converted to linux - it should be about makng apps in Linux better -and/or educating people that do not know what apps to use for special needs. Lets be serious - the more responses I see and read about Linux are not from Linux die-hards, they are from people that recently converted or have not dived into it very much. Im not saying these people don't count - But the apps are there - if you wanted to use Linux - you would learn the application better. I have created web sites, and have played with graphics quite abit. Yes - some things have taken me longer but in the end I was always happy - I guess in the end I am always surprised to see some of the comments that I read - hell- often I never reply because of this! If you want an app in linux - put pressure on the manufacturer of that app - don't talk down linux please - and to say that Linux isn't in the game ... Well .. its the second most used system taking customers from Unix, Windows, and some Mac people every day, so lets be serious ...its very much in the game..When google, Merril Lynch, Lowes. etc use Linux ...ITS VERY MUCH IN THE GAME. IT will slowly trickle down - hell - Microsoft would not be thinking of releasing its next OS for free if it (Linux) wasn't in the game.

    21. Re:How can we take this seriously... by drgonzo59 · · Score: 2, Insightful
      Good point. What you mentioned is exactly the difference between the learning people get in an applied college vs a 4 year university. Someone learning from an online university or from a 2 year applied school will learn to do things by memorizing the menu paths. For example they might say to themselves "To add a new layer I must click the 3 menu from the left, scroll down two item, then click the third on the right" or something like that. That works fine for a while but put that person in front of a different operation system or a different program that has pretty much the same functionality as the one he learned, just different menus -- and they are completely lost!

      That is why I think it is important to teach the basics _and_ the applied stuff together. So while someone learns Photoshop or GIMP they would also learn why there need to be layers, what is DPI, what is a color space, what is kerning, hyphenation and other general stuff like that, not just memorize the sequence of menus. This doesn't apply just to Photoshop, it applies to everything. For example when dealing with programmers, I can tell right away if they graduated from a 2 year school or a 4 year one just by talking to them for 1 minute. The ones from an applied college will ask me what languages I know and boast as to how many they know. Someone from a 4 year college would instead ask me what kind of programming paradigms do I like to use to solve a problem (procedural, functional, object oriented etc.), or they'll ask me about wether I prefer to use Prim's or Kruskal's algorithms for a minimum spanning tree problem. And stuff like that.

    22. Re:How can we take this seriously... by b0r1s · · Score: 2, Insightful

      Missing one more point: some shops don't care what individuals use as long as the job gets done, but interact with other companies that use "industry standard" (read: Photoshop) document formats. For example, my company exchanges files with some of the biggest ad agencies in the world - if you think you're going to use a Linux desktop and force a designer at (insert ad agency here) to change, you're f'in crazy.

      Even if you like Gimp, the first time you have to use someone else's computer to open a CS2 PSD, you're going to raise some flags for the pointy haired bosses of the world.

      --
      Mooniacs for iOS and Android
    23. Re:How can we take this seriously... by iamlucky13 · · Score: 1
      Did you read the article ("Why photoshop tops linux most wanted apps list")? Nobody suggested that Dreamweaver is more important than Photoshop.
      The survey, no. The article, yes. Let me pull the quote out for you. It's from the first couple lines even.
      Scott Morris and I were both surprised to find Adobe Photoshop anywhere near the top of the list in early results. Quicken, my own favorite, QuickBooks, Dreamweaver -- sure. But Photoshop?
      emphasis mine.
    24. Re:How can we take this seriously... by eno2001 · · Score: 3, Interesting

      Well... I'm an artist (musician primarily). That's why I got into working with computers. It's only natural that as a musician/photographer/graphic artist, I'd want to get to know more about my instrument (the computer). So learning to create music/edit photos/create original images with computers spilled over into gaining knowledge about networking, Bash scripting, compiling from source, etc... Oddly, it seems that I'm an exception. But I don't think I'm all that different from the average person. I think most people are capable of doing this stuff. 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. Our time is taken up by way too many things that should be handled by competent infrastructure.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    25. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Insults like "Idiot." get "(Score:5, Insightful)"?
      Grrreat! So smooth, fluent and civilized. gg

    26. Re:How can we take this seriously... by MichaelSmith · · Score: 1
      this is about folks who need certain tools to get things done.

      If they go to 100 workplaces and ask them what applications are stopping them from going to Linux the most common reply may well be Photoshop. But its not that simple.

      Each site will have a couple of windows only applications which they rely on. Each of these applications will be used nowhere else. These are the applications which need to be made available.

      Some will work on wine, many won't.

    27. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Please, for the love of Allah, it's 'of'

    28. Re:How can we take this seriously... by zalt · · Score: 5, Interesting

      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.

    29. Re:How can we take this seriously... by sumdumass · · Score: 2, Interesting

      Actualy the car analogy kind of parralells this exactly. Recently certain new cars started monitoring the gas caps and stuff. The also changed the way the service engine light was controled when an oil change was scheduled.

      The result of people not knowing how to work on thier car is a trip top the dealership or mechanic and a shop fee to have then reset the diagnostic code when the gas cap wasn't tight while going down the highway or when the jiffy lube forgot to reset the preventive maintinence counter after the oil change and it eventualy threw a code wich caused the engine to perform poorer.

      It appears they don't care. It seems to be a cost of living or driving. I find it insulting to have to pay the dealership $80 to turn of the check engine light when some one didn't tighten the gas cap up after refueling. It almost apears that people don' think they are getting quality unless there is alot of expesne added to it.

    30. Re:How can we take this seriously... by zerblat · · Score: 1
      The user shouldn't have to look at HTML source much, if at all.

      Actually, it's surprising that the open source community hasn't developed a really good web design tool.

      Have you tried Nvu?
      --
      Please alter my pants as fashion dictates.
    31. Re:How can we take this seriously... by sumdumass · · Score: 2, Interesting
      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.
      It comes odwn to laziness i guess. It isn't like they will be learning a new application every day insted of doing thier work. When you run the economics of it, lets asume that the artist charges $100 per hour to work on somethine and Photo Shop cost $200. So they spend 4 hours trying to do thier work in Gimp and fail, They are out $400 potnetialy earned. Now lets say they can acomplish thier work and it takes a little longer at first but then becomes as quick as in PS. They have saved $200, plus the cost of upgrades, plus the cost of new operting systems because PS will eventualy stop supporting your operating system.

      It doesn't apear to be a big loss or gain. It is just the motivation of the person your asking to try it. If they are open to new ideas, they will try it. If they are lazy and don't want to be bothered they won't. The bigest reason is that people fear change. They fear changing jobs, changing significant others, they fear moving into new homes and leaving the one thye are already comfortabe with, they fear new proceedure and resoncibilities at work. If you don't believe me, look at how many people try to fight proceedure changes and fill forms out the old way or forget to do them. You will see that they fight about every change possible unless they see an instant upside that benefits them. Gimp, i don't think has a big enough incentive to be considered a benefit.
    32. Re:How can we take this seriously... by yoyhed · · Score: 1

      You have good points, and I agree with you on the whole, but I have to point out that Photoshop is at 9.0, and they have added significant features with every major release (6 of them since you switched at 3.5). For example, the RAW support and Vanishing Point added in 9.0. I don't know if GIMP has those features now, but to some people they are necessary (and in my opinion, quite amazing) and weren't in GIMP last time I used it.

      --
      WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
    33. Re:How can we take this seriously... by WindBourne · · Score: 1

      While I will be shocked if a number of ppl move due to photoshop, the other apps make loads of sense. Quicken/Quickbooks would enable a number of quick moves, just due to security. Businesses WANT a secure system. Likewise, autocad would enable a large number of moves due to the fact that it is an engineer app. Most engineers like to save money.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    34. 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.

    35. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      but interact with other companies that use "industry standard" (read: Photoshop) document formats. For example, my company exchanges files with some of the biggest ad agencies in the world - if you think you're going to use a Linux desktop and force a designer at (insert ad agency here) to change, you're f'in crazy.

      The last time I made something for publishing in print (made a picture based on some mandelbrot fractal for an art callender), the publisher had no trouble whatsoever using the tiff and tga files I produced, he didn't even know whatever program I used to produce them and assumed it was photoshop according to a later conversation.

      So, what document format is it exactly that you are talking about here? because I believe that document/file formats are a non-issue in this case.

    36. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      The problem with Dreamweaver and any equivalent tools is that while it makes your design job a bit more efficient, this is at the price of making the site less efficient for every visitor. Your design work is a one time thing, unless you expect only one visitor, the inefficiency for them is nto a one time thing, and it causes direct cost for those running the site as well.

      A couple of weeks ago I was talking to a clothes designer who needs a website. After having looked at some things I made for others, she was wondering what I was using to build websites. She had noticed that while I use some of the things so common to sites designed in dreamweaver, that what I had made was a lot faster and smaller, and worked on every browser she tried (including the one on her mobile phone).

      I'm sure you can make decent sites in dreamweaver as well, but for me any such tools are usefull for making a layout in a visual way, but not for producing the actual code that is going to be used on a website.

      I guess that the reason I care at all is because I also host the sites I design, and it makes the hosting quite a bit less costly, resulting in better proffit.

    37. Re:How can we take this seriously... by JulesLt · · Score: 1

      But that's kind of the point.

      An O/S upgrade and new Photoshop every 18-24 months, isn't really THAT significant compared to business income (especially as it will be a business expense and therefore deductible from some sort of tax). A lot of people will stretch that cycle out even further, maybe only upgrading every second version - and there should, in theory, be some good reason for them to do this (like the new 3-D cut and paste feature in PS).

      IMO, OSS has worked enormously well with the likes of Eclipse, Apache, etc, because the audience of these programs are both capable of modifying the programs, and motivated to do so - if something annoys them about their tools, they can modify them. They rapidly change because of this input. That is as much an advantage as the fact that they're free - probably more so.

      But your typical Photoshop or Flash Studio user is in the same boat - the program is a mystery, and they can only ask for a new feature to be implemented.

      Bit like cars in a way - people have voted (with their wallets) for cars that are reliable and mysterious internally, over ones that are cheaper yet can be self-maintained. Techies often don't realise that (and nor to car mechanics, when you hear them pouring scorn on popular modern cars).

      --
      'Capitalists of the world, unite! Oh ... you have' (League Against Tedium)
    38. 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.
    39. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Ideally, no. Architects don't spend a lot of time making bricks.

    40. 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'
    41. Re:How can we take this seriously... by JohnFluxx · · Score: 1

      I agreed with you right up until you said "alot".

    42. Re:How can we take this seriously... by Achromatic1978 · · Score: 1
      So did you ever check the colour proofing?

      Admittedly, RGB processes are becoming more common with digital printers, but CMYK rules the roost. And last I checked, TIFF/TGA has ... zero ... support for stuff that is handled every single day with great regularity: spot colours, Pantones, metallic inks.

    43. Re:How can we take this seriously... by dunkelfalke · · Score: 1

      hmm, i actually always preferred cool edit (now it is called adobe audition) exactly for the ease of use

      --
      Conservatism: The fear that somewhere, somehow, someone you think is your inferior is being treated as your equal.
    44. 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.

    45. Re:How can we take this seriously... by ThePhilips · · Score: 1

      I dunno why your post was marked flaimbait.

      All my friends who deal with professional publishing say the same. Everyone in industry tried GIMP - it's just not up to the job. Or is there any one here silly enough who would cash out $600 for Photoshop (aka PS) when there is gratis alternative? All I can say is that some companies bye for most people cheaper Corel PhotoPaint - but for viewing purpses only. Photoshop with its price tag is reserved for designers only.

      PS pros prefer PS. For users who need e.g. QC/QA designer's work GIMP's GUI is bit too frustrating, but Corel's PhotoPaint is Okay.

      Most my friends designers have jobs related to printing and/or polygraphy. And all of them take part time jobs for web designe and/or development. Guess what kind of tool they use? Free GIMP? - or Photoshop they already have and know?

      For any design related job, polygraphy is sacred art. W/o understadning inner working of polygraphy and publishing one would never become good designer and would never master Photoshop. That's what most of my friends are saying. (Artistic taste helps a lot too.) Advertisement market is hugest consumer of DSP (Desktop Publishing) - Internet ad market is growing - but still just little fraction of ad market of newspapers. And most of that market is served by PS.

      In fact, I think comparision of GIMP and Photoshop is rather silly. Photoshop is built from ground zero for preparing raster graphics for publishing. GIMP has no target market. (Well, it has no market at all - it's not sold (-; ) Due to that difference, GIMP cannot mature into good publising tool: there is no strong driving force before/behind it. Adobe has some obligations before its customers - and it wisely chooses to listen to them. GIMP doesn't experience that kind of user pressure.

      It doesn't mean GIMP is bad. It's great tool for preparing content for Web. Most of Linux GUI is made in GIMP. It also has excelent scripting. In fact, from what I know, GIMP's scripting is the most wanted feature by most of my PS-pro desginer friends. (One my friend learned subset of Perl and installed Linux specifically for GIMP/Perl tasks.) Photoshop has something to learn from GIMP too.

      --
      All hope abandon ye who enter here.
    46. Re:How can we take this seriously... by VJ42 · · Score: 1

      I have a dual boot machine, the only reason for the Windows install games and dreamweaver. I'm happy with Gimp, and almost everything else, I just like the dreamweaver IDE; I never use the wsiwyg aspect of dreamweaver, but I still can't find a FOSS program that competes with it. Maybe it's just a case of sticking with what I'm used to, but I really would like to see Macromedia do a dreamweaver port to Linux.

      --
      If I have nothing to hide, you have no reason to search me
    47. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      And eps does? no problem, can produce that as well, need some other file format? Seldom is that going to be the problem.

      You are right that lack of support of CMYK in the Gimp is a major problem for using it for creating print ready material.

      That was however nto the argument I replied to, that argument was about producing file formats that the publisher can read.

      If you can produce it with the Gimp (which you obviously cannot when needing CMYK, so that is really a non argument here when talking about file formats) and you can save it with the Gimp, then you can usually read it with Photoshop and the like.

      Indeed only suitable for cases where RGB will do.

    48. Re:How can we take this seriously... by Jackmn · · Score: 1
      Look, I love the penguin. I feed the penguin. But don't put down folks WHO YOU NEED to cross over. Yes, some folks NEED these tools because of some PHB. Help them make the case. Don't act all 1337 because you can hand script some animation foo on GiMP.
      We don't need anybody to cross over.
    49. 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.

    50. Re:How can we take this seriously... by Achromatic1978 · · Score: 1
      I'm willing to grant you that.

      I could argue about obscure stuff like SciTex (though I could be wrong there) and LZW/ZIP TIFFs (and there, too, but it's been a while since I've seen GIMP), but you made your point. :D

    51. Re:How can we take this seriously... by lixee · · Score: 1

      This is probably redundant, but what's wrong with installing Photoshop with Crossover Office? I have never had any problems at all with it.

      --
      Res publica non dominetur
    52. Re:How can we take this seriously... by The_reformant · · Score: 1

      Pro tools is a sequencer, cool edit / audition is an audio editor. They do completely different things (although Pro tools does have audio editing facilities built in).

      One big difference is that audition (cool edit in its latest form) is almost exclusively for destructive off-line processing whereas pro-tools and other sequencers are primarily for non-destructive online procesing.

      Further there are much more "scientific" and much higher quality tools available for pro tools than there is in cool edit or audition. The parametric eq in audition for example is a complete mess. The UI is horrendous!

      Linux will never see a large market share for these kind of specialist tools, in the case of audio part of this is due to poor audio interface support under linux (are there any good multi in/out cards that will work under linux?) and partly because applications which are used by industry specialists (photoshop, pro-tools, adobe premiere etc) are hugely expensive to develop and require enormous amounts of manpower. The original article missed the key difference about these pieces of software and thaqt is that they are extrememly focused on the workflow that professionals use. Until OSS has the funds or manpower to support really analysing how software is going to be used as well as the technical magic done in the processing engine then i dont expect there to be any major changes.

      --
      I have discovered a truly remarkable sig which this post is too small to contain.
    53. Re:How can we take this seriously... by Fred_A · · Score: 1

      I'm not sure what the cold fusion rds thing is, however any KDE application can open a URL, so in the file open/save dialog of kedit (in your example although you probably want to use kate instead if you want a plain graphical editor, but also look at things like QuantaPlus), or in the file manager, you can use a filename like :

      sftp://server.example.com/path/file.html

      You can use a number of protocols in place of the sftp bit such as webdav, smb, etc. See the available kioslaves in your KDE installation.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    54. Re:How can we take this seriously... by talon001100 · · Score: 1

      Let me ask you a question regarding this... Do you currently have a job? Are you punching someone else's clock? Because unless you are like me and other freelance designers out there that simply have NO TIME to worry about petty arguments over which OS is better, who DO NOT punch anyone else's clock but our own, then your comments should be taken with a big handful of salt. I came from a network engineering position, where my every waking hour was consumed by thoughts like yours, praising the glory of the penguin. But once i was laid off, and found that I could make it on my own without the need of "the man" spoon feeding me tidbits of money every other week, did i realize, that the tools make all the difference. It's all about speed, accuracy and reliability of your product that you care about. And please dont bring up how one OS is more reliable than another, we all know linux wins hands down. the fact of the matter is, is that the hosting is not your concern. as long as it's inexpensive to the client, has massive features, and is always up.

      I know X/DHTML in and out like the back of my hand, and all that goes with it. but I choose to use dreamweaver because quite frankly all the FOSS editors out there cant hold a candle to it's refined quality for preview. I use GIMP for minor image alterations. but on the whole, i use Flash 8 for putting together backdrops, boxes, etc on my sites. it's easy, quick, and the fonts render out much nicer than in GIMP when saved. I do not use photoshop, but plan to buy it soon. mainly because GIMP lacks many of the OotB adjustment features that photoshop has, example.. brightness/contrast detection/cropping. this is a very useful thing that i have not found in gimp. and if it is in there then it's burried. as with many FOSS things, they're made by people with networking or programming backgrounds, and haven't the slightest clue what accessablility is. a refined application is one where a group of people that know all about the competitions products, people that know how to program, and the users of the product all sit together and collaborate before coding begins, or is released.

      at any rate, i use both COTS and FOSS simultaneously for what needs done. as i do with my desktop OS. however i mainly stick with windows for desktop, and linux for servers. it just makes sense. does it suck that is makes sense? yes, but i have no time myself to fix it. maybe someone with more time on their hands like people with jobs can.

    55. Re:How can we take this seriously... by John+Nowak · · Score: 1

      Oh please. You're telling me if you sat someone down in front of a computer before and told them to "show that thing they typed about foo", they'd say:

      1) Well, okay... that thiing has words in it... I must need to open Microsoft Word!
      2) OKay that thing I want to show is called a file. I have no idea how I could know it is called a "file" and not a "document" or "letter" or "paper" or anything else... I just do! Magically!
      3) I know that in order to "show" something, I need to find the "open" command. Does it make any sense to "open" a piece of paper? No, of course not! But I know I have to do it, yes sir... and I know it is under file!
      4) Okay so I've selected File -> Open from the "menu" (because I know they're called that, even though they don't list food on them! -- magically!!). Now I'll just navigate the file hierarchy... ... You get my point. If you don't let me clarify: You're an ass.

    56. Re:How can we take this seriously... by rubicelli · · Score: 1



      Whu? Adobe has patented CMYK? My eyes! My eyes!

      (Somebody's going to have to explain to my copy of Corel PhotoPAINT, which happily does CMYK, that it's violating an Adobe patent.)

    57. Re:How can we take this seriously... by BigSven · · Score: 0

      It's a miracle to me why noone has sat down and spent some days implementing a "Save for Web" plug-in for GIMP. There is definitely lots of interest in such a feature. The reason it doesn't exist is not that GIMP was not meant to be used for web production. It's simply because noone has coded it yet.

    58. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      Whu? Adobe has patented CMYK? My eyes! My eyes!

      Not exactly, they have patents on ways to do colorspace conversion however.

      (Somebody's going to have to explain to my copy of Corel PhotoPAINT, which happily does CMYK, that it's violating an Adobe patent.)

      Maybe, just maybe Corel licenses those patents from Adobe? Maybe they have found a way around it and can afford the risk of being sued? I don't know, but I do know that in the current situation, The Gimp does not have either option.

    59. Re:How can we take this seriously... by MSZ · · Score: 1

      TIFF supports CMYK, no problem.

      --
      The moon is not fully subjugated. I demand a second assault wave preceded by a massive nuclear bombardment.
    60. Re:How can we take this seriously... by Robocoastie · · Score: 1

      Good point. Schools and colleges teach photoshop not gimp. How to books at the bookstore are on photoshop not gimp. Now yes, if you actually know how to use photoshop already chances are good you can pick up the GIMP pretty easily; but if you're an existing employee that overnight has been added one more job to juggle then learning to use GIMP is a daunting task.

    61. Re:How can we take this seriously... by Hosiah · · Score: 1
      That said I'm giving GIMP a try every once in a while.

      I've written a series of tutorials here. I did thing to address some of what you express. I've noticed that Photoshop has such a massive market share that people simply cannot concieve of doing it any other way, hence the "fog" you speak of.

      It's obviously not made for print due to the lack of CMYK-support

      I owe Steven J. Vaughan-Nichols a black eye. Here, despite the flat-Earth-misinformation, is a CMYK plug-in. For Gimp. It's a work-around, due to copyright issues.

    62. Re:How can we take this seriously... by rikkards · · Score: 1

      it is even worse than that in Windows as of Win2K. Users are not only taught that files are called documents (then wtf is the boot.ini?) they are no longer directories, they are now called folders.

    63. Re:How can we take this seriously... by SComps · · Score: 1

      It's not so much the motivation as the economics of the "downpayment." If it takes a long time to relearn something you already know and are comfortable with; that's wasting a lot of time (money) and needs to be factored into the original "cost" of the decision.

    64. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Not so fast. By the same reasoning, you could also ask, "A document designer shouldn't have to look at XML source much?"

      At some point, tools should abstract you from the raw data format. Maybe we're not there yet, but dismissing this desire out of hand seems a bit short-sighted.

    65. Re:How can we take this seriously... by SComps · · Score: 1

      nope.. not much at all. Design your site visually. Make it look the way you uhhhh designed it. Hit the code to make sure things aren't obviously going to blow up the common browsers and "ship it." It's the way things work in the world of profit and loss. Academia has the luxury of being able to ponder the exact position of a BODY tag, it's indentation, the theory and what the original author might have been emotionally thinking at the time of its placement. That doesn't mean the rest of the world works that way.

      As far as why there's no really decent GUI web design packages for linux? You hit the nail on the head right there. Linux is largely populated by the types that can't live without seeing the HTML and heaven forbids actually doing something that doesn't require a CLI and knowing the 17 nuances of command parameters to handle the task at hand.

      The GUI isn't there because the people who WOULD write the GUI balk at the idea, and the people that would USE the GUI generally aren't the people able to write the code.

    66. Re:How can we take this seriously... by jvp · · Score: 1

      CXOffice doesn't support Photoshop past version 7. Adobe is up to CS2, or version 9 at this point.

      I was doing the same thing you are, until Adobe moved on and Codeweavers/WINE didn't keep up. I've since given up on the "Photoshop on Linux" crusade and moved my photo editing to a Mac.

      jas

      --
      Jason Van Patten
    67. Re:How can we take this seriously... by Kadin2048 · · Score: 1

      Uh ... I'm going to take a stab at this one. It's because there's no advantage?

      You have to look at it from the PHB's perspective, where running Linux isn't an end unto itself like it might be for you and me. Running Photoshop on top of OpenOffice (or WINE, etc.) still requires them to buy a license for Photoshop, so there's a big incentive out the window. Plus, the users aren't going to like it and are going to bitch and moan like crazy, because it's going to be slower than if it was running natively on the same hardware. While speed may not seem like a big deal (and might not be, if you were just doing 72 or 96 dpi web graphics), somebody working with 200MB drum scans and applying filters to them isn't going to be very happy that they just lost 10% (or whatever) to emulation overhead. Perhaps if you could prove that the speed decrease, both in terms of UI responsiveness and compute-intensive tasks, was trivial, you might have a case. But it's going to be an uphill battle.

      Plus, there probably isn't going to be support for this configuration from Adobe, and companies are notoriously (and for good reason) unwilling to adopt unsupported or third-party-supported configurations on a wide basis.

      I think, some day, Adobe is going to make Photoshop for Linux. But it's not going to be very soon, because I think they perceive (along with many other commercial developers) that the platform is too much of a moving target. Plus, I think the Gnome vs. KDE thing probably doesn't help either, even if it's not a significant technical hurdle anymore to run applications developed for either one on the other, it creates a perception of a schism.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    68. Re:How can we take this seriously... by minkie · · Score: 1
      *blink* A web designer shouldn't have to look at HTML source much?

      I'm a programmer. I can't remember the last time I looked at assembly language. At one time, the idea that a programmer wouldn't know the assembler for the machine he was working would have been shocking. HTML is just the assembly language of the web.

    69. Re:How can we take this seriously... by ccharles · · Score: 1

      My conclusion so far is that while GIMP has a Photoshop resembling toolset it's really not a Photoshop competitor.

      I agree that GIMP isn't enough for graphics professionals. It's great for people like me, who occasionally do photo manipulation and image work for the web. I, too, would love to see proper CMYK support.

      it's good enough for the average guy, even though I think the UI could improve tremendeously.

      I also agree that its UI could be improved. However, as a GIMP user who has given Photoshop (also a legal license) a real try, let me say that the Photoshop UI could also improve tremendously. Neither GIMP nor Photoshop is really *easy* to use. Deciding which one is *easier* is left as an exercise for the reader.

    70. Re:How can we take this seriously... by engagebot · · Score: 1

      I was with you all the way up until CoolEdit is actually more powerful than ProTools. Apparently you've never worked in a pro studio before. The fact that you even put them in the same universe makes your lack of recording knowledge blatantly obvious. You just made a comparison equivalent to iMovie vs. Avid. Take a trip over to digidesign.com sometime.

      --
      Han shot first.
    71. Re:How can we take this seriously... by KilobyteKnight · · Score: 1
      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.
      Not too weird. And not too different from PhotoShop. Heck even most of the keyboard shortcuts are the same. If you're really a professional, you're using the keyboard shortcuts.
      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.
      CMYK support would be nice. Most photo printing places want the image in sRGB though. Those that don't can still use it. "Save for web" is a weak argument. If you're a professional, you know all about JPG compression and how to tweak it to your needs.

      The only big thing missing from Gimp is 16 bit support. There are some nice features of PhotoShop, lots of bells and whistles. Many of them quite useful. It's a highly polished product. However, there's nothing you can do in PhotoShop that you can't accomplish in Gimp (except work with 16 bit images).
      --
      When will Windows be ready for the desktop?
    72. Re:How can we take this seriously... by sbrown123 · · Score: 1

      These folks will NEVER use Linux no matter what. I'm a 24/7 Linux user myself and I know that for a fact.

      I didn't get the survey either. This complaint about Photoshop, to me, has always been a bit absurd since MOST computer users do not use Photoshop. MOST computer users get confused with Microsoft Paint so Photoshop is way out of their league. Dreamweaver is another complex tool where MOST users opt to use the more simplistic Microsoft FrontPage. Again, MOST users do not create web pages.

      MOST users use Windows because it came with their computer. MOST users don't even know what Linux is or that they can install it on their computer. MOST users, who know about Linux and that they can install it, won't even bother going through the effort since Windows works for what they are doing.

      Not everyone is a computer geek. MOST people with computers have simple needs. Linux will only make headway on the desktop by being preinstalled there. Thats just the way it is.

    73. Re:How can we take this seriously... by DuckDodgers · · Score: 1

      As an aside, it really is disappointing to see how commonplace pirating is. I know half a dozen people that use Adobe Photoshop for editing pictures from their digital cameras, and I'm the only one that paid for a copy.

    74. Re:How can we take this seriously... by crblev · · Score: 1

      "The GUI isn't there because the people who WOULD write the GUI balk at the idea, and the people that would USE the GUI generally aren't the people able to write the code."

      That's the most cogent point made yet.

      Even then it's not just about GUI. It's no suprise that the power users of applications or OS's end up scripting (Flash, 3D apps,OS scripting, etc.) They've hit the limits of the GUI design and abilities. But, like us fabulously wonderful Slasdot readers, they're not representative of the average computer user.

      Windows and Mac-based design programs are fashioned in the same framework, but vary in the quality of design. Even in this relatively similar environment people won't shift apps because the learning curve eats time they don't want to "waste" re-learning efficiences when they could be working or going to the pub.
      Learning brand new applications can be worse (ever seen Lightwave or Blender's "GUIs")? Great, even just good, GUI design is damn difficult.

      A great OS, the same applications, and a couple of great exclusive apps, or an easier GUI won't lead the masses to Linux. There's a whole host of other issues to get people to switch Apple is proof of that.

    75. Re:How can we take this seriously... by Hatta · · Score: 1

      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!

      Your first mistake is trying to use an office suite to do statistical analysis. Try using real software like R. Often you'll find that there's no exact linux equivalent to microsoft garbage because linux comes equipped with more powerful tools than a microsoft workstation.

      --
      Give me Classic Slashdot or give me death!
    76. Re:How can we take this seriously... by the_crowbar · · Score: 1

      I don't know how well OpenOffice.org Calc does statistical analysis. I do know that if you change the file extension from .txt (or whatever) to .csv OpenOffice.org Calc will import it. I haven't looked for a way to change that, but OpenOffice.org will import .txt files to Writer and .csv files to Calc. Even if it is tab delimited (which is what your comment suggested) change the file extension and try again. The OpenOffice.org Calc import wizard very closely resembles MS Office Excel.

      Cheers,
      the_crowbar

      --
      Have you read the Moderator Guidelines
    77. Re:How can we take this seriously... by hachete · · Score: 1

      I'm not a newbie wrt computers - I've worked on and off with them since 1986. My focus these days is on art. I don't really want to learn more than I have to - and I'm speaking as a poet who uses scons and Abiword to build his website. My relationship with both is as a user. I report bugs. I don't fix the problems, I work around them. If I delved deeper, I wouldn't have any time to do what I what I wanted to do - write poetry, paint, draw. Focus.

      I think linux systems are for those who wish to exchange money-up-front for time spent later with scripts, rpms yadda yadda yadda. I've spent my time in the trenches writing scripts to provide the missing bits of functionality. I've noodled with GIMP, trying to learn those extra bits and boy was it a PITA. It aint worth it if there are packages out there that will let you do it in less time and if they get it slightly wrong, well, there's slack in most things we do. My main aim in life is to produce something, not learn GIMP.

      If I can afford it, my next box will be a MacOS X machine. Linux is for the birds.

      --
      Patriotism is a virtue of the vicious
    78. Re:How can we take this seriously... by spitek · · Score: 1

      Did you actually compair GiMP to Photoshop 3.5? Have you worked in Photoshop CS? The amount of changes and updates since 3.5 is huge. GiMP has a long way to meet the demands of Professional graphic desingers, photography and printing. From profiles, to plug-ins, to pulling .raw file format off my Canon Mark II. Color profiles for high end printers. It goes on and on.

    79. Re:How can we take this seriously... by Zerbs · · Score: 1

      It clearly depends on your definition of what a web designer is. Theatetus needs to realize that some people would rather spend their time concentrating on the asthetics of their presentation on the web page and providing usefull information that's easily navigable instead of worrying about the details of a crude language that attempts to describe page layout.

      --
      "22 astronauts were born in Ohio. What is it about your state that makes people want to flee the Earth?" Stephen Colbert
    80. Re:How can we take this seriously... by DrSkwid · · Score: 1

      No, these people will NEVER use The GIMP, not Linux.

      They really, really don't care what OS they are using and most don't even know what an OS is.

      People come into our facility to use Photoshop, they pay by the hour and they don't want to use that time to learn that Gimp can't do the things they are used to. If I could sit them down in front of Photoshop 7 running on an Amiga they'd be happy.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    81. Re:How can we take this seriously... by Theatetus · · Score: 1

      Attitudes like this are why the web is 90% suckage.

      There is no such thing as a WYSIWYG web page editor.

      Let me say that again: there is no such thing as a WYSIWYG weg page editor. At best there is an editor that shows you roughly what the page looks like for many user-agents... but I stress "roughly" and "many".

      Designers of web pages can make suggestions to the rendering client about layout and presentation, but coming at it with a view that you're going to "design" a web page in the same sense you would design a printed page is idiotic and, again, is why 90% of the web sucks so bad and is largely unusable.

      --
      All's true that is mistrusted
    82. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Right... because in Photoshop when you have JPEG selected under "Save for Web" There is obviously NO way to know how to change the compression. (hint it's right near the dropdown that has JPEG in it)...

      Oh Noes! So Hidden! So confusing! rofl and you got modded insightful too, /. is so sad.

    83. Re:How can we take this seriously... by eno2001 · · Score: 1

      Actually I've worked in pro studios and seen a wide array of software/hardware combos. I used to be in the audio business. Probably the best system I worked with was a Mac based Studer Dyaxis back in the early 90s (beat the pants off of ProTools circa 1994). I've also worked with ProTools, MoTU, Reason, etc... However, these are not affordable to the home user or the home based business. So I went to what I could afford and moved to Win 3.1 first. Things were horrible back then and I pined away for a Mac but knew I'd never be able to afford one that could do what I wanted. When CoolEdit Pro 2000 came out, I'd say they far surpassed when ProTools had to offer even if the processing was not done by DSPs. It would appear that Adobe agreed with me because they bought it and it is now known as Adobe Audition. Is there better software than that? Yes. I've also used Sonic Foundy/Sony's products as well and Steinberg's Cubase VST 24. However, I can't afford to keep shelling out money for new systems, new OSes and new software every couple of years. So I've moved my audio work to Linux as well and am very pleasantly surprised by programs like Rezound (for mastering/stereo editing), Ardour (for multitrack recording with excellent effects processing), and Roasegarden (the closest thing to Cubase that Linux has going). As far as multichanel audio boards, I'm using an Event Echo Layla (20 bit) eight channel board. Very nice system compared to what I was using back in the ProTools days. Thanks to ALSA, there is plenty of support for very good multichannel boards. You won't get the top names in the business, but then again that's not necessarily bad. There are plenty of lesser known brands in all facets of life that are equivalent or superior to the name brands. The same applies to audio hardware. The fact that you think Linux has little to offer to the audio producer illustrates just how unfamiliar you are with the territory. There is little that you can do in the Mac or Windows audio world that you can't do in Linux. Hell... I can even ship my data out of my Linux box to AES/EBU for final tranfer to pro DAT to send off to any mastering house I want.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    84. Re:How can we take this seriously... by hesiod · · Score: 1

      > it is even worse than that in Windows as of Win2K.

      People have used the terms Folder and Document since long before Windows 2000. Something isn't new just because you hadn't heard of it.

    85. Re:How can we take this seriously... by eno2001 · · Score: 1

      To parent poster: This isn't really directed at just your post. In fact most of it is responses to other people. But I do address the laziness issue:

      Jesus Christ! Why do people get so riled about this subject. The accusations of "elitism" top it all off too. There is no elitism in my post. I was being nice. I acknowledge that everyone has limitations and it's not their fault. I know that my limitations for example relate to subjects like math and money/business. So I accept that other people are better at it than I am. Are they elitists because they excel at something I don't? For fuck's sake NO!!! They just have different abilities and strengths. But, I also counter that MOST people are capable of learning computer stuff. I also believe that knowing how to use a computer is as important in any computer related field as, well... breathing. But I DID say that I don't expect people to move to Linux. Some of that is due to their laziness and some of it is due to their natural limitations. How is that insulting? It's NOT. It's the truth plain and simple! If I wanted to be insulting, I'd say, "Most people can't move to Linux because they are too stupid to know what's good for them and I don't want to waste my time dealing with them. Let them have their Windows spoon feeding". Now THAT IS insulting. It's also not what I believe. I didn't say people who don't use Linux or Unix are idiots. I said people can't or won't use Linux because of laziness (caused by society not forcing them to educate themselves) or inherent limitations that are beyond anyone's control. Does that make them lesser people? Not any more than my inability to do advanced math makes me some kind of failure. Christ people!! READ why don't you?!

      Let me try this again...

      1. Linux works very well for me in every way. I haven't run into ANY application that *I* NEED (other than the occasional game) that makes me think Linux isn't ready for the desktop
      2. Windows is too limiting and costly for me
      3. Macintosh is too costly for me even if it is the best of all the OSes
      4. Windows works well for *OTHER* people and I don't fault them for using it
      5. If *OTHER* people expended some of their time making the move to Linux they'd likely feel the same way I do

      I'm always amazed by the stories I hear of people who've "tried" Linux only to find that it "sucks" in their opinion. And then when they explain why, it's because they only spent a few hours or days on it. I challenge ANYONE here who has only strictly worked on one platform (Mac or Windows) to switch and only spend a few hours or days and finding that their every need is satisfied. That's just STUPID. It's like moving into a house that needs some work and expecting it to be your dream home in a few days. If you folks have ever moved out of your parent's homes and bought your own place, you'd know that. Well assuming you're like me and you start with a teardown of the existing stuff you don't like about the house. (I have a tendency to completely rewire my homes from top to bottom, repair all the plaster using old fashioned plastering techniques, then prime and paint everything. It usually takes me about three to four years to get the house right) This is pretty typical of the average person. Now apply that to an OS switch and you'll see where I'm coming from. Look at your desktop (Windows or Mac). Unless you're a pretty boring person, it's likely that you've massively customized the environment beyond what it was like when it came from the factory. Did that take you a few hours? Days? Don't lie... unless you already had a standard desktop setup with custom wallpaper, some kind of profile to store the location of your icons, launcher bar, screensaver, etc... it probably took you quite a few weeks. But you persisted. If the same level of persistence were applied to Linux, you can make the switch. This is true of ANYONE. Even the people with some inherent limitations. The fact that that kind of persistence is lacking when it comes to something that is less well known is a failing of society.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    86. Re:How can we take this seriously... by manno · · Score: 1

      If I only had mod points. This is good, info, that should be shared.

    87. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      Oh Noes! So Hidden! So confusing!

      Being able to 'see' it if one wants to is nice, and I'd have been surprised if you couldn't set the compression quality at all. Hiding it behind 'profiles' is the issue here. Many a graphics artist I dealt with seems to believe that this 'save for web' stuff does things that they cannot do themselves, or wouldn't be able to learn or understand themselves.

      It is creating 'magic' where there is none. If Adobe wants those profiles (they are definitely usefull, why think up defaults for everything yourself all the time), they would do good to call them something like 'defaults for web', and explicitly show what such a profile does.

      rofl and you got modded insightful too, /. is so sad.

      Heh, +5 insightfull is a bit much for that post indeed.

      But it does look to me like I have a point that you are just missing or are unwilling to accept.

    88. Re:How can we take this seriously... by fitten · · Score: 1

      Nice post, but you say: They've been conditioned to believe that they need new machines every couple of years. That'show bad it is in the computer industry right now. and, while this may be true to some degree, I know many people who don't do so.

      A quick digression, what you say, in a nutshell is Moore's Law: it's the rate at which people will upgrade (based on economics and the like). The industry can move forward with process shrinks and the like at that rate and make money. Slower than that and they'll lose the market because others will supply the performance, faster than that and people will skip a generation.

      Back to the subject, there are a number of people in my family still running PentiumII and PentiumIII machines. I think my uncle still runs a Pentium(that's it, just Pentium). Those are folks who do fairly light stuff on their machines. Those who tend to upgrade every two years are enthusiasts (who will always want the latest/greatests) and those who want the tasks they do to be done faster. Take the professional content creator who makes very heavy use of Photoshop and the like. This person will want to upgrade, fairly often, to fairly good hardware. The reason is that it will hopefully cut the time to do certain tasks. This has many obvious advantages. A serious Photoshop professional would be using a fairly high end P4 or Athlon64 these days, not a PentiumIII or much less something from 10 years ago because a new system would easily cut the time down on certain tasks by at least a factor of 10.

      Still... that doesn't help people who don't want to have to get used to something. It's a sad truth simply because they could better themselves if they put the effort in, but most people simply don't want to.

      A couple of things here. First, given someone like a Photoshop professional, learning the new thing takes time, not only for the application itself but possibly the platform as well - as the OA says, it's about the plugins and stuff, too. So, spend a few weeks ironing out The Gimp (potentially lots of frustration in this task) or spend a few weeks actually doing work and getting paid? For many, that's a very easy choice. The other bit about "bettering themselves" is specious, at best. Quantify "bettering themselves". Most people don't care about the OS as long as they can get their stuff done (it works AND it is familiar). Most people don't care about where the application comes from (OSS or closed). They just want to do their thing. Saying that using OSS is "bettering" oneself implies there is something morally (or religiously) better about it than the alternatives and that would be something very hard to prove (and no, "because it's not M$" is not a valid argument).

      Me, I use Linux for a lot of things that it does well (and the applications on it do well). Likewise, I use Windows for the things it (and its applications) do well. I have no religious ties to either as they are tools which happen to be suited for similar jobs, just some better than others.

    89. Re:How can we take this seriously... by plague3106 · · Score: 1

      I find it insulting to have to pay the dealership $80 to turn of the check engine light when some one didn't tighten the gas cap up after refueling.

      Care to mention the manufactorer? Because most cars that light the service indicator because the cap hasn't been tightened enough will reset on their own after three fillups.

    90. Re:How can we take this seriously... by muuh-gnu · · Score: 1

      > Well... I'm an artist (musician primarily).
      > It's only natural that as a musician, I'd want to get to know more about my instrument (the computer).

      If the computer is the only instrument youre capable of playing, then you NO WAY can be a musician, not to mention being some "artist".

    91. Re:How can we take this seriously... by LifesABeach · · Score: 1

      I think the fundamental problem here is that there is a group of people that will not change unless their life style is impacted. As an administrator, I'm left with no other choice then. The funny thing is that the 9 to 5 computer graphics artist did all the work in getting themselves a new job. If a prospective employee cannot use GIMP, Gimpshop, or Photoshop; Then what the hell are they thinking by taking up my not-free time?

    92. Re:How can we take this seriously... by vertinox · · Score: 3, Insightful

      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.

      I take it you have not worked retail, tech support, or at a law firm.

      No, but seriously, I understand when I take my car to the garage, I am the gibbering idiot. Otherwise, I wouldn't need to take my car there. People should understand this fact on both sides of the fence.

      My car mechanic doesn't need to treat me like a gibbering idiot, but neither should I claim that I know more than my mechanic. When someone calls me for computer assistant, I don't treat them like an idiot, but they shouldn't act like they know more than me and should quietly assume to be the idiot.

      Heck, when I call my ISP, out of respect I play dumb in order to make the call go faster and make the person on the other ends job a whole lot easier than I would to try to say "hey... your an idiot... i know more than you!" because you know... If I didn't know how to fix this on my own I wouldn't have called (even if I knew it was something like a NIC card refresh etc and knew what the other person had to do... i'm not going to demean them over it).

      We are all gibbering idiots outside our realm of expertise. Otherwise, we wouldn't have capitalism.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    93. Re:How can we take this seriously... by MobileTatsu-NJG · · Score: 1

      "When you run the economics of it, lets asume that the artist charges $100 per hour to work on somethine and Photo Shop cost $200. So they spend 4 hours trying to do thier work in Gimp and fail, They are out $400 potnetialy earned. Now lets say they can acomplish thier work and it takes a little longer at first but then becomes as quick as in PS. They have saved $200, plus the cost of upgrades, plus the cost of new operting systems because PS will eventualy stop supporting your operating system."

      The reality of this situation is a bit different. Photoshop has a far greater toolset than GIMP. Most artists who are charging $100 an hour aren't doing just red-eye removal and levels adjustment. If they're a texture artist, such as myself, all of those fancy Photoshop doodads come into play. (For example, I recently upgraded from CS to CS2. The vanishing point tool is GREAT. Now I can make changes whilst maintaining perspective correctness.) The money you spend on Photoshop upgrades is peanuts compared to the speedups and quality improvements you get. For a LOT of artists out there, GIMP is not Photoshop. GIMP is so not Photoshop that you do NOT make more or equal money by saving the cost of Adobe upgrades etc. Maybe one day this will change, but not today. Like or hate proprietary software, Adobe has a big big incentive to keep turning out the new and interesting features. Even with the latest release of PS, they've managed to keep it interesting. I just can't see the GIMP ever reaching a point where they get that innovative.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    94. Re:How can we take this seriously... by rikkards · · Score: 1

      No need to be snarky. I figured it was older than that but it was around the release of Windows 2000 when someone "corrected" me on it.

    95. Re:How can we take this seriously... by Theatetus · · Score: 1

      I think Zerbs and the rest of my responders are missing the point, not me. If you don't know HTML you're not a web designer. You may be a designer but you're not a web designer. Similarly if you don't know how printing works you're not a print designer. If you don't understand how your designs are implemented by the rendering technology, you aren't a designer for that medium.

      --
      All's true that is mistrusted
    96. Re:How can we take this seriously... by xtracto · · Score: 1

      Hello Linux fanboy.

      I use Linux, I like Linux. I know about R, SAS and SPSS. If you read my post again you may notice the part where I said that the deadline for my paper is near so I *do not* have time to learn a new staistics oriented language. Because of that I didnt proceeded with R (FYI I downloaded it and tested, I even followed the begginers tutorial from the documentation).

      Now, about the Microsoft garbage thing, wow, great way to display your fanboysim. If, as you imply Microsoft Office is garbage then, I do not want to know what is the status of OpenOffice as it has always been an attempt to rip-off Microsoft Word/Excel applications with some more-than-that wanna be presentation and drawing applications (granted, I like the *idea* of OO Draw but, i even used them to make some nice graphics on EPS to use in latex, but I saved in version 1.99 and THE FILE WAS NOT LOADED CORRECTLY ON 2.00 WTF ).

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    97. Re:How can we take this seriously... by Anonymous Coward · · Score: 0
      So it boild down to only to factors:


      (1) Gimp does not handle CMKY color model
      (2) The user interface is not a clone of Photo shop and you are not willing to learn it.


      Argument #2 is why people stick with MS Office.

    98. Re:How can we take this seriously... by Theatetus · · Score: 1
      I'm a programmer. I can't remember the last time I looked at assembly language.

      The analogy there is no good. Compilers guarantee (roughly at least) a consistent translation from HLL to assembly to machine language. There is no similar guarantee in HTML: there is not a rendering contract that guarantees this or that HTML will render this or that way on the screen.

      If a designer doesn't know html, he's a graphic designer. He is not web designers because he doesn't know how his designs render in the medium.

      --
      All's true that is mistrusted
    99. Re:How can we take this seriously... by xtracto · · Score: 1

      1. Linux works very well for me in every way. I haven't run into ANY application that *I* NEED (other than the occasional game) that makes me think Linux isn't ready for the desktop
      2. Windows is too limiting and costly for me


      Name ONE thing you can do on Linux that you can do on Windows

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    100. Re:How can we take this seriously... by eno2001 · · Score: 1

      Did you mean "can't"? I'll assume you did, otherwise the list would be long and pointless.

      Here is one example. There is no equivalent of the 'sleep' command in Windows NT 4 or 2k. I had to write my own sleep command in VB script just to accomplish a simple "sleep 5s". And since VB script is such a fucking mess, my script would only run on some machines unless I wanted to do version checking. You shouldn't HAVE to do version checking in a script!! I'm very well versed in CMD scripting and I can say it's very lacking when compared to Bash. Now... if I add Cygwin to the mix, then Windows becomes far more usable but very kludgy. The main problem is that Microsoft seems to abhor following the standards of structured programming. VB script sucks in so many insane ways. CMD in Win2k is still lacking. I've seen some things expanded in Win2k3, but I don't care much at this point. I will say that Monad looks interesting because of it's ability to pipeline data in an OOP fashion. But that's a feature that I've been able to live without so far and it won't be making it into Windows mainstream any time soon. Thats' just one example.

      What I've seen is that with an out of the box Windows installation, you CAN'T make a system do to many interesting things without buying a bunch of add ons. With an out of the box Linux system, you've got much more comprehensive development tools that allow you to make your box do pretty much anything you want it to. Hell, I made my own CUSTOM PVR (that works worlds better than the crap software that was bundled with the capture card) using Linux and all I needed to do was compile one external driver for the PVR-250 card and write a bunch of Bash scripts utilizing Zenity for GUI interaction. Everything I needed was in my base Fedora Core 3 installation. I didn't need to buy anything other than the PVR-250... I challenge you to do the same with Windows.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    101. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      If all Linux users had the same attitude as you, Bill Gates would be the dancing in his office. I am glad not all Linux users are like you, because if they were Linux on the Desktop would always second and Microsoft would always be a Monopoly.

    102. Re:How can we take this seriously... by xtracto · · Score: 0, Troll

      I will answer just to some of your comments, as one answer covers all of them.

      . I had to write my own sleep command in VB script just to accomplish a simple "sleep 5s". And since VB script is such a fucking mess, my script would only run on some machines unless I wanted to do version checking.

      So, you can program a bash script and manage to install a tarball but you whine for a pretty basic "idiot-based-language" VB script?. Cool that you only have this *some machines* problems with a sleep thing that can be done in other ways (or at the end, you achieved in your own way); there are things that can NOT be done on any Linux flavor, like for example using some hardware. Darn...

      using Linux and all I needed to do was compile one external driver for the PVR-250 card and write a bunch of Bash scripts utilizing Zenity for GUI interaction.

      Whoopewho, Compile? wow 1337. On windows you only have to double click on a program and it will be there!

      Everything I needed was in my base Fedora Core 3 installation. I didn't need to buy anything other than the PVR-250... I challenge you to do the same with Windows.
      I do not care how much did it costed, as a lot of companies. Remember, the advantage of OSS is not in the price. If I wanted a PVR I would just bought a softare (you could do it too!.

      Now, I will conclude saying again, I am not against any OSS, but it is not true that Windows
      is too limiting compared to Linux. All the new applications available for Linux are "replacements" of Windows applications. That is not bad, they make some functionality available.

      The difference is that with Windows you pay for the software so it just work while on Linux you have to make it work. Some people do not want to waste their time on that. The same way as I do not want to waste my time looking at the motor in my car, I just want it to take me from my office to my home.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    103. Re:How can we take this seriously... by civilizedINTENSITY · · Score: 1

      Apparently you were in such a hurry that changing the file extension was too much for you? I'm sorry, I meant the Document extension. You know, your text Document has a name, and after the dot...oh, your main OS hides file extensions? Never mind, I can see that it is too complicated.

      It is funny that you seem think that word processors and spreedsheets that look somewhat alike must be copying from Microsoft, since Microsoft didn't originate either type of application..."rip off" was a little extreme, and lotus couldn't make the look and feel arguement stick. Hence, the "rip off" is now the standard. In terms of Microsoft Office being garbage, I think "garbage" is a little extreme. Still, it isn't best of breed.

    104. Re:How can we take this seriously... by civilizedINTENSITY · · Score: 1

      How about the RME Hammerfall and Hammerfall Light? 52 channels and full 24 bit resolution,

    105. Re:How can we take this seriously... by rossifer · · Score: 1

      If you can produce it with the Gimp (which you obviously cannot when needing CMYK [...] )

      A CMYK plugin is here. It's just a simple starting point, and the jury is out on whether it infringes Adobe's patents (but apparently, Adobe has not patented CMYK per se, but some of the color transform algorithms, so it's quite possible that the GIMP could reach the same destination from a different path).

      Regards,
      Ross

    106. Re:How can we take this seriously... by Anonymous Coward · · Score: 0
      It is possible to open a delimited text file into cells in OOo Calc. I've done it before, but can't tell you how right now, because I'm at work where I don't have OOo available. What I haven't been able to do is copy and paste delimited text into cells from the clipboard, this is indeed aggravating.

      On another note, you might not want to do too much statistical analysis in MS Excel. (Maybe not in OOo calc either) http://www.practicalstats.com/Pages/excelstats.htm l/ http://www.csdassn.org/software_reports/gnumeric.p df/ http://www.daheiser.info/excel/frontpage.html/

    107. Re:How can we take this seriously... by eno2001 · · Score: 1

      Guess again. I play, piano, guitar, upright bass, didgeridoo and compose my own music as well as produce others. But I still consider the computer to be the ultimate musical instrument. It's much more varied than the others and much more expressive if you know how to use it. Of course, what else should I expect and a jealous AC... ;P

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    108. Re:How can we take this seriously... by mr_dillrod · · Score: 1

      Some of you Linux guys don't get it... real graphics pros want Photoshop, and they want it on a Mac. But EVEN IF Adobe CS were completely ported, I *still* wouldn't use Linux cos the GUI is so DAMN UGLY, a little worse than Windows' I'd even argue. I'll admit that Linux kicks Windows' ass for the simple fact that Windows runs like crap and is not *NIX-based at all; (these two elements seem to go hand in hand generally)... (I would only defend Mac OS 9 for it's interface and not performance.) It may sound silly and superficial, but once you get used to the comparatively GORGEOUS Aqua interface of OS X, the beautifully anti-aliased type, the ease of configuration, the wealth of apps (Pro Audio/Video/Graphics) (minus games), AND AT THE SAME TIME pretty much all the great *NIX stuff available to you also, it's really just the ultimate ***ing workstation. There is no other way to put it. And it's hard to ever imagine (for me, anyway) wanting to use a Linux box, though I can appreciate the philosophy behind it. Just my annoying thoughts, j/

    109. Re:How can we take this seriously... by sumdumass · · Score: 1

      It apears to b a a kia. this is just one of the stories floating aorund ab out it.

      I'm aware that some of the codes will reset themselves over time if the problem is corected. OTOH, while the code is present, the performance and possibly the fuel economy of the vehicle is reduced wich makes a check engine light seems worse then it is tricking mom and pop into having it looked at.

      slashdot has covered some of this before. MY understanding is that some codes on the KIA (and other cars) can only be reset with the dealerships diagnostics equiptment. It is locked out to other mechanics or ordenary people. Somethign about copywrite DMCA and such. I don't no if the bill in that link eventualy passed or not.

    110. Re:How can we take this seriously... by Crizp · · Score: 1

      You're correct, in that graphic artists should save images as JPEG using "save as..." and 90% quality or so. But "Save for web" is not made for large photos or print material.

      The really, really nice thing about "Save for web..." is that, for the web designer, you can see exactly what the compression does before you save it, and it has superb tweaking options for the end result to be the perfect compromise between size and looks. The result need not be crap, you just have to know what you're doing.

      If a graphic designer uses "save for web" in the way I think you mean ("gee, i'm uploading this to a web site, so I should use save for web, right?"), they should really read more Photoshop documentation.

      Somehow I assume you know this already, and that I'm just preaching to the congregation here... oh well.

      On a side note, I try out the Gimp once in a while, but I can never seem to get around the interface. I know that's because I've been using PS since version 3, and the workflow of Gimp is just different.

      Still, some of the ways of doing things in the Gimp seems cumbersome and unnecessary. I'm talking about selections, copy/paste etc. And can you actually use polygonal selection in the Gimp? If it's there, I haven't found it. And that's the tool I use the most in PS.

      Sure, magnetic lasso and freehand selection is fine, but there's nothing like the accuracy of zooming in to 600% or more to cut something out pixel by pixel by pixel :)

    111. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Automatic upgrades for almost any app you use.

    112. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      The really, really nice thing about "Save for web..." is that, for the web designer, you can see exactly what the compression does before you save it, and it has superb tweaking options for the end result to be the perfect compromise between size and looks. The result need not be crap, you just have to know what you're doing.

      Definitely, I really like the 'preview' it gives you there. I just wonder why that is not an optional part in the normal 'save as' dialog.

      If a graphic designer uses "save for web" in the way I think you mean ("gee, i'm uploading this to a web site, so I should use save for web, right?"), they should really read more Photoshop documentation.

      Agreed, and that is indeed what I am running into quite a bit.

      Somehow I assume you know this already, and that I'm just preaching to the congregation here... oh well.

      On a side note, I try out the Gimp once in a while, but I can never seem to get around the interface. I know that's because I've been using PS since version 3, and the workflow of Gimp is just different.


      Yes, and at times it is just not very logical and cumbersome.

      Still, some of the ways of doing things in the Gimp seems cumbersome and unnecessary. I'm talking about selections, copy/paste etc. And can you actually use polygonal selection in the Gimp? If it's there, I haven't found it. And that's the tool I use the most in PS.

      Sure, magnetic lasso and freehand selection is fine, but there's nothing like the accuracy of zooming in to 600% or more to cut something out pixel by pixel by pixel :)


      Copy/paste I find pretty easy (and am pretty fond of the 'paste as new' feature), its selection that can be a real pain. I haven't found the feature you are looking for but then, I'm not in much need of it so I didn't look too hard. I often need inverted selection by color, and both programs do that pretty well.
      At any rate, in my experience accurate selection in the Gimp is often between a bit bothersome and utterly painfull if you need some random shape in a busy picture.

    113. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Photoshop's clumsy, cluttered and archaic user interface is suitable only for use by people who do nothing but Photoshop year-in, year-out, and have been at it since Photoshop came out. As a person who has had to use Photoshop on Macs and Windows, I say Photoshop's UI desperately needs an overhaul.

      Problem with TheGIMP is the lack of good training tutorials. I've read The GIMP's official hard copy user manual. It's a reference, but not a user manual. It covers the tools and everything about them - except how to use them to accomplish imaging processing work tasks ...

    114. Re:How can we take this seriously... by Mr2cents · · Score: 1

      You shouldn't be afraid to open notepad and write the HTML code directly.

      *blink*

      A web designer using notepad as an editor? ;-).

      --
      "It's too bad that stupidity isn't painful." - Anton LaVey
    115. Re:How can we take this seriously... by marcosdumay · · Score: 1

      If instead of writting a C program to reformat your doccument before feeding it to excel (why it is a win for excel again?) you could replace every space with a comma and get a default csv file that can be opened by every spreadshit you can think about (and statistical analysis tollboxes).

    116. Re:How can we take this seriously... by Anonymous Coward · · Score: 0

      Nicely said .... now if only they could port autocad :(

      Hehe jokes aside though, the parent is correct, in my office it is impossible for me to use linux because or industry is so dependant on m$ software (AutoCAD, Adobe, Project, and Office). Although there are linux alternatives out there, the simple fact of the matter is that i cant get our clients to swap over to linux too. It doesnt matter how good you think the linux application is or how fast you think it is growing, if I cant get a client to access my data (converters are not an option) then linux is just a pipe dream for me.

      PS: Please GOD .. help the OpenDocument format!

    117. Re:How can we take this seriously... by The_reformant · · Score: 1

      this is exactly the problem, linux users insist that the product are already good enough the show stopper in this case is no VST

      --
      I have discovered a truly remarkable sig which this post is too small to contain.
    118. Re:How can we take this seriously... by budgenator · · Score: 1

      My stepson is a "PS or Bust" type so finaly I set him down with some images a copy Of Gimp and PS Elements. I told him to do some trivial manipulations in PSE, then I did the same in Gimp much faster using the keyboard shortcuts. It was on then, he finaly gave up when I proved to him not only could I do anything faster in Gimp than He could in PSE, but that I could do anything he could faster in PSE too, because I knew the keyboard shortcuts. Perhaps the "bad" user interface in Gimp is an advatage.

      I'm not sure about the state of CMYK in Gimp, but I'm surprised that Gimp is stuck in 8 bit color considering cinepaint forked from Gimp and does 32 bit color in real professional formats from kodak and pixar

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    119. Re:How can we take this seriously... by xhrit · · Score: 1

      I know about kioslaves. I use smb , ftp, & kaudio quite a bit. There is no rds kioslave to be found on google, only mentions that someone should make one. I would, but I'm not sure how... how legal it would be, that is.

    120. Re:How can we take this seriously... by boschs_haywain · · Score: 1
      Linux will never see a large market share for these kind of specialist tools, in the case of audio part of this is due to poor audio interface support under linux (are there any good multi in/out cards that will work under linux?)

      Check out the Alsa Soundcard Matrix, e.g. M-Audio and RME, probably a couple others for multi-line. Of course the whole driver/open specs issue is as relevant to sound cards on linux as it is with any other hardware.

      BTW, there are seemingly infinite numbers of cool sound apps available for linux. As is also generally the case they tend to be small apps that do one thing really well as opposed to Pro-Tools/CuBase ultimate behemoths that attempt to do everything (new, now with proprietary lock-in!).

      Are they generally used to exclusively populate a "pro-audio" toolkit? Probably not by your definition of "pro", not yet anyway.

      Do professionals use FOSS audio tools on linux to earn their livings? Yes absolutely, everyday. For that matter, the GIMP, Inkscape, Dia and mplayer? Natch.

      Indispensible resource page: dave phillips linux-sound.org

      Also one of the highest signal to noise mailing lists I've seen on teh Intarweb: linux-audio-user

      [momentary regret] 'What have I done, I've slashdotted lau!'[/momentary regret] Oh well, whaddyagonnnado? Barton
      --
      Huh? Oh yeah, that.
    121. Re:How can we take this seriously... by dylan_- · · Score: 1
      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.
      This is a bit silly, as I think it should at least ask what to open in if there's any doubt. But you were trying to be too complicated. Just drag and drop the file onto Calc and it'll work exactly the same as Excel. Alternatively, if you rename the file from .txt to .csv it'll work too.

      As for Calc lacking options: well, you claim it but it has exactly the functions you required. I don't know what you're complaining about here.

      BTW, if you're planning to do a lot of stats work later, it really is worth taking the time to learn a real stats package. It'll save you a lot of work in the long term. SPSS is quite easy to pick up.
      --
      Igor Presnyakov stole my hat
    122. Re:How can we take this seriously... by Lew-the-nerd · · Score: 1

      Thanks, well said. As a 4 hour/day PS user I just don't have the time or incentive to spend learning Linux and then learning GIMP for a dubious (in my case) ROI. Port over PS and I'll crank up the Linux servers I have and drop my Windows box.

    123. Re:How can we take this seriously... by Fred_A · · Score: 1

      It probably depends where the person who implements it is. In most places reverse engineering a protocol/program for interoperability purposes is legal. In the US I'm not sure.

      However I'm not convinced that using the RDS thing is actually better than SFTP or FISH or something more standard along those lines. But then my only experience with DreamWeaver was a 2 second glance at a screen while someone was using it. :)

      --

      May contain traces of nut.
      Made from the freshest electrons.
    124. Re:How can we take this seriously... by xhrit · · Score: 1

      I'm not sure that RDS is 'better'.

      Using SFTP or FISH or something on a php site that lives on a linux box is fine for new clients, but not the old clients with cold fusion sites on whindows servers that by nature get less and less secure the more software that is run on it.

      The info I found on google seems to indicate that RDS uses crafted HTTP POSTS to communicate with the server, and that it might be possible to create an RDS KIOSlave as a wrapper to the HTTP KIOSlave and use HTTP as the transport, only using the RDS KIOSlave for generating and parsing the data for/from the server.

      I would do it but I am in the 'Land of the Free'(TM) so what I want to do is most likely illegal.

    125. Re:How can we take this seriously... by Fred_A · · Score: 1

      Technically, if the protocol can be reverse engineered (I expect it shouldn't be very difficult since it doesn't do much after all) it shouldn't be very difficult to implement.

      As you point out, the only obstacle is potentially legal.

      Judging from a quick search, there has been one mention of it on the KDE dev list which didn't seem to get any attention and that was that. Nothing has happened since. So between vaporware and a very remotely possible potential vulnerability with an added ssh server, I'd pick the latter. I can relate to the sane practice of limiting the amount of unnecessary software on production machines though. :)

      --

      May contain traces of nut.
      Made from the freshest electrons.
    126. Re:How can we take this seriously... by EspressoMachine · · Score: 1

      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.

      Don't blame the tool. It's not that the result of the save for web feature is inherently crap, it's that the user is selecting a compression rate that's far too severe, causing artifacting and all sorts of ugliness. The settings you're telling them to use will result in an image that's not suitable for web publishing...1280x1024 and low compression? That's gonna give you a huge (for the web) file size, for starters. And most users wouldn't be able to see the whole image, or worse, their browser may resize it, most likely to an odd fraction of the original size, resulting in that great jaggedy look. Unless you're doing the unthinkable and using element attributes to resize the image in the page. *shudder*

      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.

      Photoshop's save for web tool could never be seriously accused of explicitly hiding what it does from a user. If anything, it's got to be overwhelming for most users because of the amount of control it offers. You can apply multiple compression rates to areas of an image using alpha channels, along with a dearth of other features, all right there in the right sidebar. At any rate, how is simply selecting "90% quality or better" disclosing the process to the user, or giving them any control?

      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?

      Wow. You obviously don't understand how this whole compression thing works. You can't just assume that one setting will work for every image. So much of it depends on the content of the image, since what you're really deciding is "how much of this image can I throw away before it's noticeably degraded?" Of course, if you're just using the lowest compression/highest quality setting (bad idea for the web), this is moot.

      I guess it's a good thing you're not a graphics artist, but given you're comments, I also have doubts about your web development expertise.

      --
      Despite conventional wisdom, I've discovered you can blame a guy for trying. It's called "attempted murder".
    127. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      Don't blame the tool. It's not that the result of the save for web feature is inherently crap, it's that the user is selecting a compression rate that's far too severe, causing artifacting and all sorts of ugliness. The settings you're telling them to use will result in an image that's not suitable for web publishing...1280x1024 and low compression? That's gonna give you a huge (for the web) file size, for starters. And most users wouldn't be able to see the whole image, or worse, their browser may resize it, most likely to an odd fraction of the original size, resulting in that great jaggedy look. Unless you're doing the unthinkable and using element attributes to resize the image in the page. *shudder*

      Heh, how about a webserver that can resize the image before sending it to the client? It really works well, and having the full scale pictures on the server means you can let the client chose what quality to use.

      Photoshop's save for web tool could never be seriously accused of explicitly hiding what it does from a user. If anything, it's got to be overwhelming for most users because of the amount of control it offers. You can apply multiple compression rates to areas of an image using alpha channels, along with a dearth of other features, all right there in the right sidebar. At any rate, how is simply selecting "90% quality or better" disclosing the process to the user, or giving them any control?

      Ok, I think I wasn't very clear there. Of course 'save for web' offers a zillion things that you can adjust, but there is nothing that makes it 'for the web', its just a usefull set of options and a previewer. As a matter of fact, all the things it has could easily be optional features in the normal 'save as' (just have an advanced button there)

      The issue I am running into with photoshop users is that they think that just using 'save for web' will produce a file suitable for publishing on the web. Are those users at fault for not learning the tool they are using? sure, but as I pointed out a few lines back, there is no reason for it to exist to begin with.

      So you are right that it is not hiding options so much as encouraging people to not use the tool properly.

      Wow. You obviously don't understand how this whole compression thing works. You can't just assume that one setting will work for every image. So much of it depends on the content of the image, since what you're really deciding is "how much of this image can I throw away before it's noticeably degraded?" Of course, if you're just using the lowest compression/highest quality setting (bad idea for the web), this is moot.

      If that is what you send to the browser, then its a bad idea, yes. It never occured to you that you do not actually have to do that, but rather, can decide on scaling and compression when a browser asks for the picture, and at that moment you can make sure the browser isn't going to scale it down because it didn't fit and that kind of nonsense. This is not suitable for all pictures, and depending on use can become a bit expensive on the server, but it is very usefull when used properly.

      It also never occured to you that the web designer may want to scale the picture him/herself to have more flexibility while implementing the design?

      You do want a high quality source for those things however.

      I guess it's a good thing you're not a graphics artist, but given you're comments, I also have doubts about your web development expertise.

      That is only because the possibilities for a different approach never occured to you.

    128. Re:How can we take this seriously... by cloudmaster · · Score: 1

      I don't NEED anyone to cross over. My desktop works. My servers work. I need applications to continue to be supported so I don't have to maintain them myself, but I could not care less if some "web designer" converts or not. Actually, if he's already got tools that work, then I NEED him to stay the hell on his tools that work - not to use some other half-assed system just because some cock on slashdot thinks that everyone in the world needs to use Linux. Everyone doesn't. "Don't act all leet just because you use Linux and therefore think that everyone else should too." Maybe spend some time helping Linux to succeed where it actually has half a chance - on the server side. The desktop "war" is over. Windows won. Years ago. There's no "until Linux catches up" because it's not gonna. And this doesn't make a damned bit of difference because Linux is doing very well in the server room, and is working out very well on the workstations that would have run some other *nix - this is where I would "like" some more progress. Even then, I don't care. Why do *you* care what someone else runs if their needs are being met by something else? Why do you feel a need to make my already very good Linux experience more like some piece of crap I dumped 10 years ago?

      BTW, .NET already has several supported components on Linux. Doh.

    129. Re:How can we take this seriously... by EspressoMachine · · Score: 1

      A couple of things first:

      You posited that graphic artists should know how different compression levels will work out. That's just not feasible. If they need to resize, etc. later, I'd hope they're saving a full-sized, layered, PSD file that they can go back to and make adjustments for different outputs. My point was that they can't just "know" what result a compression setting will give, since the same level of compression can give drastically different results depending on the image.

      I think we're in agreement now about the "save for web" (I too often wonder why they chose that instead of just giving you those options standard when you save as...but whatevs) not being the i>source of the problem.

      Now:

      You are indeed correct, I of course did not consider the possibility that you may be compressing and resizing through image processing on the server. It's my (admittedly bad) knee-jerk reaction to assume that most people who consider themselves web developers are really just hobbyists who know little to nothing about the web or actual development. If you've been in the industry for any length of time, I hope you understand my reaction is rooted in the frustration caused by the erosion of credibility afforded to actual web developers, due to the aforementioned folks.

      That being said, I must apologize for that jab. I wasn't in a particularly good mood when I replied, and you have shown yourself a gentleman by your response. For that, I salute you.

      --
      Despite conventional wisdom, I've discovered you can blame a guy for trying. It's called "attempted murder".
    130. Re:How can we take this seriously... by SillyNickName4me · · Score: 1

      If you've been in the industry for any length of time, I hope you understand my reaction is rooted in the frustration caused by the erosion of credibility afforded to actual web developers, due to the aforementioned folks.

      Definitely. Oh, and thanks for taking the time to reply, it is appreciated.

  2. They have a point... by Sensible+Clod · · Score: 5, Interesting

    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
    1. Re:They have a point... by hackstraw · · Score: 2, Insightful


      I agree. Gimp is pretty cool, but Photoshop is the "industry standard".

      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.

      Apps drive the OS. Linux/UNIX has all of the server stuff available, and that is where it is. OS X has tons of good apps. Linux on the desktop? Maybe when brand name apps are available (and usability increases, yada yada).

    2. Re:They have a point... by DavidHOzAu · · Score: 1

      As powerful as GIMP is, I find myself struggling to complete tasks that would be easier in Photoshop.
      There are two words to largely explain that: Layer Effects.
      Until GIMP has blending effects that can be directly linked to individual layers, it won't be as power. Just look at Outer Glow, Bevel, and Stroke. There's nothing like drawing with the paintbrush and that nice halo automatically appearing along the digital paint's border.

      Also: Groups.
      GIMP can't forming groups from layers, and there is no way to hide (NOT the same as switching them off) a whole swathe of layers in the Layer Dialog without merging them. Photoshop can collapse groups, which is an obvious plus for organising a picture. If I am inking a piece of fanart for someone, I don't want to have to look through all those layers when they are for the other character I am no longer working on.

      The other thing I didn't mention is vector masks, which is pretty much self explainatory.

    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:They have a point... by larry+bagina · · Score: 2, Insightful
      Well, Cocoa is a superset of the OpenStep specification, which GNUStep aims to reproduce. Porting GNUStep to OS X is mostly a recompile, Cocoa to GNUStep could require a lot of work.

      Photoshop, however, is Carbon based, so it doesn't even apply.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    5. Re:They have a point... by signingis · · Score: 3, Interesting

      /me muses

      Wouldn't it be nice of Apple to port Cocoa and Carbon to Linux/X11/Xorg...

      It couldn't be *that* hard...

      --

      I prefer a void in conversation to a vacuous one.
    6. Re:They have a point... by gravyface · · Score: 1

      I agree. Gimp is pretty cool, but Photoshop is the "industry standard". I know quite a few Graphic Designers who grew up honing their skills with traditional mediums (photography, print, canvas, etc.) and swore that they'd never take a "computerized" Graphic Design job, simply because of how unnatural Photoshop felt in a creative sense. Obviously they got over themselves (and the learning curve) but I'd doubt they would want to go through that again with some other new application like GIMP. Personally, I've always found that Photoshop is extremely powerful but awkward and unforgiving for a new user, regardless of design skill -- and no, I have never been under the impression that it would turn a color-blind hack into Picasso.

      --
      body massage!
    7. 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.
    8. Re:They have a point... by Lesrahpem · · Score: 1

      The only reason you can't is because of Apple. There is no reason aside from the greed of corporations.

    9. Re:They have a point... by Anonymous Coward · · Score: 0

      But Photoshop is already a dual API project. Obviously they've done it once, and are maintaining it. A third time is a long project for some interns and maybe a lead full timer...
      It wouldn't be easy, but it's very doable. And if they chose Gtk or QT they'd have a platform which actually gets ported to other platforms! Instead of being glued to native API's ;).

      I think his point was that the hard stuff works on a Unix. It's just the interface that needs a rewrite for other *nix.

    10. Re:They have a point... by mini+me · · Score: 1

      the MacOS APIs (Carbon and Cocoa) do not exist on other platforms.

      In a loose sense, Cocoa does. There's YellowBox, which is essentially Cocoa, not to mention GNUstep. Cocoa on OS X has evolved so they aren't entirely compatible anymore, but with some care you can technically write a Cocoa program that will run on other platforms.

      Also, Photoshop is no stranger to X11. It's doubtful they maintained the X11 version, but who knows? It might just be a recompile away from running on Linux.

    11. Re:They have a point... by AgNO3 · · Score: 1

      No there is not a unix version of Photoshop. Photoshop is a carbon app not a cocoa app. Adobe is pretty not happy about the rewrite coming to make it work on intel Macs because there are no Carbon APi's for Intel OS X. and Havning had to use Filmgimp now Cinepaint http://www.cinepaint.org/ (lol and the status of that link should tell you something. I can tell you that having used photoshop since version 2.0 that gimp sucks to use. I mean jesus there is not even a keyboard short cut to change the brush size. (maybe now but in 2003 I couldn't find it nor was one listed in the docs.) I mean come on how basic a thing is that? OK mark me a troll.

      --
      OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    12. 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.
    13. Re:They have a point... by typical · · Score: 1

      Well...

      The idea of simple free markets is that it's okay for companies to be greedy, and things just all work out. Of course, in the real world, there are a lot of exceptions, but it works well enough as a model to use for some things.

      While it is a little annoying that Apple's APIs are only available on, y'know, Apple's OS, it's not really unreasonable, IMHO, any more than it would be to expect MS to port Win32 to Linux and freely release it.

      I get irritated when I think that people are trying to *deliberately* introduce incompatibilities for the sake of incompatibility. However, that isn't happening here. Apple was trying to address a need for rapid application development with Cocoa. Okay, they aren't giving their platform away, but I can't really fault them for that. They're playing fair -- the market needed a feature, they implemented.

      Now if they *sued* anyone who tried making a Cocoa-compatible implementation for a different platform, then I'd be upset -- but there's no evil conspiracy (or at least, one is not required to explain Apple's actions).

      --
      Any program relying on (nontrivial) preemptive multithreading will be buggy.
    14. Re:They have a point... by Durandal64 · · Score: 1
      No there is not a unix version of Photoshop. Photoshop is a carbon app not a cocoa app. Adobe is pretty not happy about the rewrite coming to make it work on intel Macs because there are no Carbon APi's for Intel OS X.
      Wrong. Apple has ported the Carbon API to x86 OS X. Otherwise the Finder wouldn't be a universal binary. Adobe is unhappy because they finally have to move to Photoshop over to Xcode.
      and Havning had to use Filmgimp now Cinepaint http://www.cinepaint.org/ (lol and the status of that link should tell you something. I can tell you that having used photoshop since version 2.0 that gimp sucks to use. I mean jesus there is not even a keyboard short cut to change the brush size. (maybe now but in 2003 I couldn't find it nor was one listed in the docs.) I mean come on how basic a thing is that? OK mark me a troll.
      I don't know about troll, but you're certainly misinformed.
    15. Re:They have a point... by Karma+Farmer · · Score: 1

      So perhaps someone should start a project similar to WINE, to add Carbon and Cocoa API compatibility.

      I bet someone with strong marketing skills could make a shitload of money doing that.

      Oh, wait...

    16. Re:They have a point... by Anonymous Coward · · Score: 0

      Are you claiming that Apple did not *deliberately* withdraw the OpenStep runtime for *nix and Win32? Boggle. Fact: They took a cross-platform API and dongled it to their shiny hardware.

    17. Re:They have a point... by mrchaotica · · Score: 2, Informative

      What do you mean, "once it's completed?" GNUStep is fairly "complete" now. However, the problem is that it's targeting compatibility with the old OpenStep standard, not the assorted changes that Apple made with Cocoa (of course, it doesn't help that Cocoa is a moving target). It's pretty stupid IMHO, but unless somebody forks it it'll never be fully possible to compile an arbitrary Cocoa program for GNUStep without having to make changes (although programs that only use the subset in common with both -- such as TextEdit -- will work fine).

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    18. Re:They have a point... by dfjunior · · Score: 1

      There is indeed a unix version of Photoshop, but unfortunately it went stale somewhere around v3.0.1 Used it a bit on Solaris. I seem to remember that there was one for SGI/IRIX but I can't track down the CDs to verify that.

    19. Re:They have a point... by Paraplex · · Score: 1

      I use photoshop professionally daily and the word "compile" scares the shit out of me. There is no way I could afford to take the risk and jump into linux while the elitism exists. That said, I would *love* to be able to get into my software apps and edit them if I chose to, but this should never be the first option. I want usability first and configurability second. (think maya, very usable, but should I want the hacker element I can get in there and write command line style... photoshop and final cut pro continue to patronise me with their closed source & limited options)

      bring the application developers to linux (adobe, macromedia etc), and back *one release* of linux for each industry. Make it pretty, make it *extremely* easy to use/install and make sure I am not having to make compromises/risks in time, quality or expense and I will convert in a second!

    20. Re:They have a point... by Lehk228 · · Score: 1

      that sounds like a very simple GUI change (for grouped layers) and could even be done reverse compatable with the existing format by appending a series of characters at the end of each layer name indicating which group it was in and whether or not it is visable

      --
      Snowden and Manning are heroes.
    21. Re:They have a point... by AgNO3 · · Score: 1

      Yeah I know about that one. it was for Irix and Solaris. I used it on both. I was only refering to the OS X carbon one. But I was wrong about that too. The cool thing about the Irix version is that wouldn't it have had to have been 64 bit to run on the r5000 mips chip? (or r4xxx chips)

      --
      OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    22. Re:They have a point... by dfjunior · · Score: 1

      I think they were both 64 bit, no?

    23. Re:They have a point... by lelkes · · Score: 2, Insightful

      Ever heard of GNUstep?

    24. Re:They have a point... by arodland · · Score: 1

      Here's another suggestion... Gimp for Win32 has a plugin loader that allows most (windows) Photoshop plugins to operate. Would it be possible to rig up a system similar to MPlayer's plugin loader which would allow these plugins to work on other x86 systems? The main issue would seem to me to be library dependencies; AV codecs are generally easy because they just do a lot of math without calling out to any other libraries; I don't know how true this is of photoshop plugins. Anyone able to clue me in?

    25. Re:They have a point... by scottgfx · · Score: 1

      Adobe did have a version of Photoshop running on SGI systems a long time ago. I believe it was Photoshop 3.

      --
      It's mandatory to wash your hands before returning to the land of Dairy Queen.
    26. Re:They have a point... by Anonymous Coward · · Score: 0

      Cocoa exists on other platforms. It's called GNUStep.

    27. Re:They have a point... by dido · · Score: 1

      Well, I believe you are incorrect, at least about the part where GNUstep aims compatibility only with the old OpenStep standard. According to this FAQ entry:

      GNUstep aims to be compatible with both the OpenStep specification and with Mac OS X. It should be easy to write an application that compiles cleanly under both GNUstep and Cocoa.

      Yeah, I suppose it's true that Cocoa's a moving target, but I don't think they can make it move as much as you seem to fear: doing so would make it an impossible platform to develop for. I believe the goal would be to make it possible to easily use autoconf or something like it to smooth out the differences between platforms, making porting apps (and writing cleanly portable ones too) a lot easier.

      --
      Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.
    28. Re:They have a point... by Ilgaz · · Score: 1

      As an end user used Slashdot Linux for 1 year, it always amazes me that people "love" OS X yet they don't use WindowMaker or AfterStep which are similar desktop implementations carrying "openstep" mark.

      Less users, less bug reports, feedback and lack of enthusiasm for people actually work on these sleek and modern desktop window managers.

      (Gnome users: WindowMaker is _compatible_with Gnome although you live "foot instead of start menu" experience when you use gnome/kde)

    29. Re:They have a point... by Anonymous Coward · · Score: 0

      So, it's possible to learn GIMP. And? All that means is that GIMP is free if your time is worthless.

      Amazingly enough, most designers and artists find that their time is really rather valuable, and continuing to buy Photoshop upgrades is actually rather less expensive for them than it would be to totally demolish their entire working environment and rebuild it from scratch using amateur tools that nobody else in the industry uses.

      Sorry, but ideology stops dead when it hits the breadline. I've got a family to feed, and I'm not going to watch them starve just so RMS can feel good about gaining another convert to his commu^Wfree software utopia.

    30. Re:They have a point... by Hosiah · · Score: 1
      I've got a family to feed

      And I suppose the users of FOSS image editing tools in this article let their families starve.

      So to recap: you come on as an anonymous coward to flame somebody for writing tutorials so the person who wants to learn *can* learn. Whose time is worthless, again?

    31. Re:They have a point... by cluening · · Score: 1

      Oddly, I have the exact opposite problem - as powerful as Photoshop is, I find myself struggling to complete tasks with it that would be easier in Gimp. I bet it has more to do with what one you're more used to using than anything else.

      Of course, I can easily recognize that Photoshop is a lot stronger than Gimp in many areas (CMYK, for example). But Photoshop also has that "funding" thing and that "several years head start" thing going for it. Since Gimp is still very actively under development, I'm not too worried about those though.

      --
      Posted from the wireless couch.
    32. Re:They have a point... by lxs · · Score: 1

      GNUStep is already being used to port programs from OSX to Linux.

      One example that springs to mind is Oolite, an OpenGL Elite clone, written in Objective C and Cocoa for OSX and ported to Linux using the GNUStep libraries.
      It's a fun game too.

    33. Re:They have a point... by lxs · · Score: 1

      Oops messed up the link: Oolite

    34. Re:They have a point... by Kadin2048 · · Score: 1

      Ah, you have a fine sense of humor, my friend.

      Why don't they just send 1,000 free shares of their stock to every Linux developer, while they're at it? Hell, maybe Steve will dress up in a Santa Claus suit and give free iBooks to everyone, too.

      Apple has created the MacOS so that it's easy to port Linux/UNIX applications to it, but they have no great incentive to create a path for porting applications away from it.

      I can run the GIMP on MacOS if I want (and have been able to for a while, although it got easier recently, since the newer versions of the MacOS include X), but it'll be a cold day in hell before you can run a Carbonized app like Photoshop on Linux. And that's exactly the way Apple wants it.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    35. Re:They have a point... by AgNO3 · · Score: 1

      uh the solaris and irix? I would think so. But the OS X one is not.

      --
      OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    36. Re:They have a point... by Kadin2048 · · Score: 1

      ...and back *one release* of linux for each industry.

      Everybody has their own pet theory that they use to explain why Linux on the desktop isn't quite there yet. Here's mine: it's because there isn't a "standard version" of Linux, and to a developer, that's scary.

      That's not to say that there's just one version of Windows, but at least it's a pretty clear playing field. You can read a one-page summary and pretty much understand the various versions and who uses them and which one you want to develop for. With Linux, the situation isn't all that clear. If you make RHEL your target distro, are you going to be losing everyone who uses SuSE as potential customers? What about the Asian market and their distributions? Do you develop for KDE or Gnome? Or create your own widget set completely independent of either? What's your performance going to be like, and how do you ensure user experience without alienating customers? There are seemingly a lot more factors involved.

      A while back, I thought we might get a partial solution to this problem (others would disagree with me as to whether it's a problem or not -- I think it is, because frankly, I want an OS and not an ecosystem) when IBM was talking about dumping Windows for Linux. That would have put 300,000 employees and a major software/hardware producer firmly behind one distribution (I think it was RHEL). Of course, it never happened -- maybe they were just wrangling for a better deal on XP licenses or something.

      I guess this situation, call it 'fragmentation' or 'diversity,' depending on your point of view, is the price you pay for not being held hostage by one vendor. However, I think there's a limit to how much marketshare an OS can have, when there isn't one widely-used and supported face for the outside world to deal with.

      I think there are a lot of commercial software houses would make Linux versions, if there was such a thing as "Linux" to make a binary distribution for. I think, eventually, one of the major commercial distributions is going to come out as the clear winner and we'll effectively have this (like it or not), once the period of expansion into new markets that we're in right now stops.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    37. Re:They have a point... by mrchaotica · · Score: 1

      Actually, I have used WindowMaker and AfterStep (and I'm writing this on an iBook). Let me tell you, though, OS X is a lot more than just the window manager -- it's the Services and Applescript and Dashboard/Exposé and being able to easily type special characters (option-e, e = 'é') and the various included apps (e.g. iTunes) and perfect hardware support and easy configuration and so on and so forth.

      And then, on top of all that, is the fact that the old (NeXT)-style window managers aren't quite as easy to use as Aqua. For example, most people probably like the menus on top of the screen better than having them in a right-click menu, the Dock works better in Aqua (between the automatic scaling and resizing, the fact that both apps and windows are shown in the same list, etc.), and Aqua is better graphically (e.g. videos keep playing in the Dock, you can see the Z-order better because of the shadows, etc). It also doesn't help that the NeXT-style WMs look old -- compare Aqua's OpenGL-accelerated "genie" minimize effect that shows window contents vs. WindowMaker's "spin" effect that only shows the window outline rectangle.

      Then, finally, there's the fact that on Mac OS, everything is designed to work with the OpenStep-style system. In contrast, with GNUStep there's only relatively few GNUStep apps, and then everything else is GTK or QT or whatever. Using GNUStep feels like being a second-class citizen.

      Belive me though, I would like nothing better than for GNUStep to be as good as Mac OS -- and, more importantly, more similar to Mac OS. For example, think of how great it would be to have GNU Darwin + GNUStep + Mac-style stuff under the hood (e.g. HFS+ with metadata, plists, launchD instead of init/cron/whatever... everything where Mac OS is different from Linux or BSD) + (and this is most important) binary compatibility with Mac OS in an easy-to-install distribution. It wouldn't have to look the same way, but if it acted the same it would certainly make admin-ing my non-Apple boxes easier!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    38. Re:They have a point... by mrchaotica · · Score: 1

      Oh, that's good news (apparently they've added that goal since the last time I checked, because it wasn't there before)!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    39. Re:They have a point... by TooFarGone · · Score: 1

      They should write a whole suite of applications for this kind of thing. More compatability! More extensions! Then people can rave about how much they love their GiMP Suite, and everyone else will think they are very very strange! It'll be great! i've been wanting to use that joke for years 8-)

    40. Re:They have a point... by Anonymous Coward · · Score: 0

      How the hell are you going to have binary compatibility with OS X (a PowerPC platform) on a non-Apple box?

    41. Re:They have a point... by KevinColyer · · Score: 1

      I too find the Gimp a mindbogglingly difficult piece of software to use and have rarely completed any serious task in it. Perhaps I would struggle just as much with Photoshop: I could never get my head around layers.

      I have been looking at Krita recently and instantly feel more at home with it. But it is too early to to really say I have made more progress with it!

      I do think competition in this area is needed and I think that Krita may heat up the pace of development of Gimp too.

    42. Re:They have a point... by mrchaotica · · Score: 1

      LOL! You haven't been paying attention to the last 50,000 Apple stories, have you? First, Mac OS runs on x86 now, and second, there exists this little thing called a Universal Binary. In fact it's always existed for OpenStep; if you go way back I'm sure there's some software that was distributed as 68000/x86/Sparc, even...

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    43. Re:They have a point... by Sithgunner · · Score: 1

      Now, for real graphic designers who has always used Photoshop, I may understand that it is troublesome to try a different interface, but the problem is, I hear all these claims from everywhere. "Photoshop is easier, GIMP interface sucks"... So, how much of you actually BOUGHT the Photoshop because you needed it? Isn't it that you people kept ripping and ripping and downloading Photoshop illegaly and got used to it? Even before there was any Photoshop Elements, the cheap version of Photshop was around, on the internet it sounded like just about anyone had Photoshop for their graphic purpose... If you're the one complaining GIMP interface sucks because you're used to your RIPPPED Photoshop, please take a moment and rethink what you're doing. Because it sounds real rubbish.

  3. 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 uhmmmm · · Score: 1

      Maybe this is just because I used GIMP first, and still use it more often than photoshop, but I find the GIMP easier to use. There have been countless times where I want to do something (the thing that comes to mind right now it merge two layers) where it takes me a while to find it in the photoshop GUI. In GIMP, merging a layer with the one below it is a simple as right-clicking on the layer and choosing "Merge Down". I've forgotten what it is in photoshop again, but I definitely seem to recall it was more mouse-clicks to do. And that's an operation I do fairly often - it shouldn't take many mouse-clicks.

    2. Re:GUI perhaps? by iamlucky13 · · Score: 1

      After a few quick hours fooling around with GIMP, I got a pretty good handle on where everything is, and I have no trouble using GIMP for all my image work. Granted, I've used photoshop only on rare occasions, so my experience is far from enough to allow me to trash talk it, but I think it's more a matter of what people are familiar with than serious flaws in GIMP.

    3. Re:GUI perhaps? by Anonymous Coward · · Score: 5, Funny
      "I mean seriously, it seems to be designed to hide functions and impede work, not t'other way round."
      So, err, you want GIMP to hide work and impede functions?
    4. Re:GUI perhaps? by stubear · · Score: 1, Offtopic

      Ctrl-E. Wow, that was so difficult. Either that or you go to the layers palette menu and it's one of the options listed.

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

      Apple-E. No mouse clicks at all.

    6. Re:GUI perhaps? by Shelled · · Score: 3, Insightful
      Which part of the Gimp GUI?

      1. The right-click-on-photo part that brings up every command?
      2. The pull down menu above the photo that brings up every command?
      3. The floating toolbox that brings up every command?
      4. The customizable tab box which permits instant access to your most important subset of commands?
      5. That near every subset of commands can be 'torn off' as a floating toolbar?
      6. 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?
    7. Re:GUI perhaps? by JahToasted · · Score: 5, Interesting
      Actually I was using GIMP before I came here. Yeah the interface sucks. I have to have an entire virtual desktop reserved for it alone, and even then there are dialogs that pop up behind the window. I have to spend more time resizing windows than actually working. And if you have a lot of images open the taskbar groups them so that it takes two clicks to get to anything.

      Why not have a nice tabbed interface?

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

      Its pretty sad when its obvious to everyone what the problem is, yet its still the same thing after what, six years?

    8. Re:GUI perhaps? by miyako · · Score: 1

      While the GIMP GUI definitely could use some work (though it has been better since version 2) there is more to the problem than redesigning the GUI. While GIMP has some nice features, in my experience Photoshop has a much better painting engine. There are a few things gimp either doesn't support or does not do quite as well as Photoshop that make it unsuitable for some things.

      --
      Famous Last Words: "hmm...wikipedia says it's edible"
    9. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      Oy, tell me about it. I prefer having my document window maximized, but this means the toolbox is *never* where I need it. Whenever I want to switch tools, it always takes me a sec to realize the box is hidden, and to find it in the taskbar and bring it back up front. It's mentally jarring, kinda like getting a popup while web-browsing (though this thankfully doesn't happen so much nowadays).

    10. Re:GUI perhaps? by c_forq · · Score: 1

      I've forgotten what it is in photoshop again

      This seems odd to me, because the reason I always stick to photoshop is I can easily figure out how to do any funtion I know exists. It seems everything is logically placed in menus, and there are keyboard shortcuts for everything. I also love the fact there are usually about 5 ways to do any given act.

      --
      Computers allow humans to make mistakes at the fastest speeds known, with the possible exception of tequila and handguns
    11. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      All of it. The entire Gimp UI is horrible and this is coming from someone who only uses Linux. You can argue about it all you want but that's not going to convince anyone to switch over and use it. This is exactly why the Gimp will never catch on. Professional graphics designers tell you that the UI is horrible and then instead of listening to suggestions and making it better the Gimp community argues with them and tells them that they're wrong and that they're simply conditioned to use Photoshop. Then they wonder why nobody uses it...

    12. Re:GUI perhaps? by Air-conditioned+cowh · · Score: 2, Insightful

      7. The file selector that doesn't look anything like what the user is used to in either Windows and KDE. In Windows it is sometimes a challenge to find "My Documents" due to the way roaming profiles are configured in some corporate environments. I haven't tried Gimp on Mac to know how out-of-place it's file selector is there.

    13. Re:GUI perhaps? by slashdotnickname · · Score: 1

      Ctrl-E. Wow, that was so difficult.

      No, pressing Ctrl+E is not difficult... but intuitavely discovering that, given GIMP's interface, is.

      I'm no graphics artist, but I've been using GIMP for years on my photos... for a time it was the best free graphics program you could get for Windows... or was, until I discovered another great open-source program, Paint.NET. For my needs the difference is like night and day. Interfaces DO matter, and Paint.NET's is just more intuitive (proof of that is that I haven't felt the need yet to read any of their documentation... if they even have any!).

    14. Re:GUI perhaps? by Keith+McClary · · Score: 1

      Ahh, so that's how it works!

    15. Re:GUI perhaps? by strider44 · · Score: 1

      To start off with I want to say I agree with you, but I'll just give a bit on why it's like that. Gimp is based off GTK+ (the Gimp Tool Kit) which is the basis for Gnome. Though yeah, the GTK has a horrific file selection browser that's supposedly designed to be "user friendly", Gimp doesn't actually have all that much to do with it and GTK is pretty well separate from Gimp now so you shouldn't blame Gimp but GTK.

    16. Re:GUI perhaps? by dbIII · · Score: 1
      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.
      There's always ImageMagik instead - if you want a graphics program with millions of options which you really can only get to from the command line. Only photoshop is photoshop - if you only know photoshop then for everything else you really do have to read the manual guys.

      How many people really need photoshop for their job anyway? For those people you give them Macs, expensive printers and other expensive software because it is entirely justified. Many people who have photoshop use it for preparing photos of their kiddies for printing on work time - and could do the just just as well with almost any graphics package and gimp is certainly overkill. I'm sure to graphics professionals a flame war over gimp vs photoshop would look like a couple of kids arguing over crayons.

    17. Re:GUI perhaps? by Farmer+Tim · · Score: 1

      I've forgotten what it is in photoshop again, but I definitely seem to recall it was more mouse-clicks to do.

      Hide any unwanted layers, go to the "Layer" menu, select "Merge Visible"; so by my count, as few as one click-hold-select-release. It may take two more clicks, depending on whether you have layers you don't want merged, but it's a more powerful function since it can be applied to arbitrary rather than sequential layers (that is, you don't need to drag layers into the correct order to save a click somewhere else in the process).

      Plus, since the command is in the clearly labelled Layers menu (which would be the first place most rational people would look for layering functions), you aren't required to guess whether right-clicking on a particular window might bring up the option you want.

      --
      Blank until /. makes another boneheaded UI decision.
    18. 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...

    19. Re:GUI perhaps? by mrmeval · · Score: 1

      Agreed. And why in the hell do they ghost out options then not explain why they are ghosted nor give me the option of doing what ever hoodoo they want to enable the options?

      I dislike a billion windows, modal windows, popups, etc. but fixing that is near impossible.

      I should have a button that says "stupid Gimp" or "Photoslop" GUI functioning and have all the menus, look and feel, etc, etc ad infinitum ad nausium instantly change to reflect that. I've complained of this before about window mismanagers with hostile results.

      --
      I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
    20. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      Correct, that is a good list of reasons why the GIMP UI is *garbage*.

    21. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      And there's really a difference between GTK and GIMP for end users who only want it to f#$%ing work?

    22. Re:GUI perhaps? by mobilebuddha · · Score: 1

      i love it.. a response w/ ctrl-E gets "off-topic", a response with "apple-e" gets "informative."

      gotta love the slashdot crowd.

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

    24. Re:GUI perhaps? by Magic5Ball · · Score: 1

      1. One menu bar is enough. Really. Functionality does not need to be distributed across 2 or 3 windows that hide each other, or become hidden by the canvas.
      1a. "Dialogs" ?!? Why not put that under Tools or Windows where users expect to find it, just as almost every other program does?
      2. I don't need every command available through a context menu, just the ones that are... in context. That means someone from the GIMP development team needs to learn how users want to use the program.
      2a. OOo doesn't expose every function through right-clicking the document. Word/WP users have no problem accessing Writer's functionality.
      3. Can we please slurp the functionality from the file command to identify files by content as well as by extension? Making assumptions about file contents by extension was never universally popular, even in the Windows 3.x days.
      3a. Seriously, not depending on file extensions will make handling image files with multiple data streams easier in the near future. Real digital cameras can output single files with JPEG, TIFF and RAW data.
      4. The customizable interface is technically impressive, but it is no substitute for understanding the needs of the users. In that respect, Photoshop is superior because it incorporates input from typical, non-power users, into the development process, and includes a default interface that works well out of the box for the vast majority of its intended audience.
      5. GIMP is a great tool, if its intended audience is tinkerers who understand and have time to customize the interface to easily get at the advanced functionality. It's a poor tool for artists who trained and work on one of the professional platforms (Adobe/Macromedia, Corel) and expect things to be in certain places. Distributing Gimpshop with the standard package would go a long way to getting some $100/hr artists to invest their time looking at the GIMP.
      6. A great tool would offer sufficient incentive for the current Photoshop users to incur the cost of relearning the interface. Can GIMP be this tool? A decent graphics artist or photographer can pay for a Photoshop license with less than a day's work.
      7. Will my third-party or homebrew Photoshop filters work with the GIMP?
      8. Assuming GIMP has the same functionality as Photoshop, what's the switching cost in time to learn a new interface that doesn't offer anything more, and doesn't play well with the current workflow? If you want me to use it for anything more than cropping screenshots for on-line, the GIMP needs color management, Pantone support, CMYK support, the ability to read and write PDF, EPS and TIFF formats, and the ability to work with TT, OTF and PS fonts, in UTF-8 and Unicode. The lack of color management and proper channel support are deal breakers in almost every non-trivial print production process. /Photoshop user for six years in print and on-line //Disappointed that requests for essential print features in the GIMP have been ignored for four years ///The GIMP developers should get one or more of the profressional design or photography associations to sponsor a weekend retreat where artists and developers can get together to exchange knowledge. While much functionality requires some poking to expose, much functionality also does not exist, or is unusable in its current form.

      --
      There are 1.1... kinds of people.
    25. Re:GUI perhaps? by Anonymous Coward · · Score: 1, Insightful

      If it doesn't offend you then why don't you just shut the fuck up. Oh wait. You're offended by the fact that someone ELSE could be offended by something you're not offended by. Why don't you just shut the fuck up.

      I hope that by NOT calling you a "motherfucker" that I didn't offend you.

      Fucking gimp.

    26. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      By contrast, of course, to the elegant simplicity and beauty of the Photoshop GUI.

    27. Re:GUI perhaps? by killjoe · · Score: 1

      "Its pretty sad when its obvious to everyone what the problem is, yet its still the same thing after what, six years?"

      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. Open source projects tend to be driven by the users and the developers and more precisely by "contributors". In most open source projects the user contributors vastly outnumber the developer contributors. They are the ones hanging out at IRC asking and answering questions, filing bug reports and helping the developers debug the application by repeatedly installing, patching, and compiling the unstable tree.

      If the majority of the contributors don't see the tabbed interface as being a priority then it won't happen.

      My suggestion to all the people bitching about how GIMP sucks and how much they hate using it (why are you using it then?) is to become a part of the community. Contribute and if enough of you contribute enough then your needs will probably be taken care of too. Failing that you could always take up a collection and offer a bounty.

      I think it's a little unseemly to bash people who give you something for free. If you don't like it you are under no obligation to use it. Just steal photoshop like everybody else at /. does.

      --
      evil is as evil does
    28. Re:GUI perhaps? by jonom · · Score: 1

      I taking it you didn't try to right-click and select "merge down" in Photoshop?

    29. Re:GUI perhaps? by jonom · · Score: 1
      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?

      I guess you're not a fan of tabbed browsing either?

    30. Re:GUI perhaps? by unapersson · · Score: 1

      "Plus, since the command is in the clearly labelled Layers menu (which would be the first place most rational people would look for layering functions), you aren't required to guess whether right-clicking on a particular window might bring up the option you want."

      You aren't in The GIMP either:

      Layer -> Merge Down

      in the top level menu.

    31. Re:GUI perhaps? by lifeisgreat · · Score: 5, Interesting

      It's odd, isn't it.

      Fact: Many users have experience with Photoshop and the GIMP.

      Fact: Most of those users find Photoshop's UI to be vastly superior, or at least the GIMP's UI to be vastly inferior.

      Fact: Those in charge of the GIMP dismiss such experienced users in the field as feeble-minded ignoramuses.

      My $1,000,000,000 prediction: this comment will be just as applicable 3 years from now.

    32. Re:GUI perhaps? by KiloByte · · Score: 1, Informative

      they sink right to bloody bottom of the window stack

      This is a problem with Microsoft Windows(tm)(r)(C)(a)(b)(c)(e)(f)(g)(h), not with GIMP. Having separate windows lets you set them up freely; if you want to switch to some other problem, go ahead -- this is what the other desktops are for. But if you are restricted to an ancient single-desktop scheme, then yes, MDI can alleviate your problem a bit.

      Thus, it's not GIMP what is a festering pile of crap. It's the lesser image editors' tendency to accomodate misdesigns of the past.

      On the other hand, once you learn something, you tend to shun all different designs. I've used Turbo Pascal (WordStar keybindings) as a kid for many years, and now I use jstar exclusively, disregarding vi and emacs as crap with anal-retentive user interface, even though I do know that in theory they are superior. This can explain why people like you dislike the new, ergonomic interface and want to keep the old MDI style you're used to.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    33. Re:GUI perhaps? by tetabiate · · Score: 1

      would you expect better from gtk?

    34. Re:GUI perhaps? by Air-conditioned+cowh · · Score: 1

      Yes, understand about the GTK+ bit but this really is a problem.

      The first thing a user needs to do is find the document they want to open followed by finding where they want to save it. If they hit roadblocks doing that then they aren't likely to use it further.

      The only place for a GTK+ file selector is on a Gnome desktop. Windows, KDE, Mac and other window manager users should not have to suffer the same misery. It must surely be possible to use a file selector from a different library according to the window manager being used? Doesn't Open Office do this?

    35. Re:GUI perhaps? by Daengbo · · Score: 1
      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).
      I guess that This means that you're using Windows? It's window manager is exactly the reason why MDIs caught on there in the first place.
    36. Re:GUI perhaps? by Anonymous Coward · · Score: 1, Interesting

      Uh, "most users" stay the fuck away from The Gimp and have repeatedly said exactly why. If the devs are only listening to their suckups in the IRC channel, then that's exactly why they have produced a profoundly unpopular program that is nearly universally rejected by the graphics community.

      Oh, and if the Gimp "community" is filled with clingy little turds like you, it's no wonder people aren't lining up to join.

    37. Re:GUI perhaps? by howlingmadhowie · · Score: 1

      the gimp was the first image manimpulation program i really worked with. about a week ago, i had to do some image manipulation on a windows machine with photoshop, and i found it very difficult to use. things were just in the wrong places. i ended up giving up and sending the files over my apache server to my linux laptop. i couldn't find a way to get photoshop to resize an image and preview what the image was going to look like. i imagine it's possible, but i couldn't find it.

    38. Re:GUI perhaps? by Daengbo · · Score: 1
      3. Can we please slurp the functionality from the file command to identify files by content as well as by extension? Making assumptions about file contents by extension was never universally popular, even in the Windows 3.x days.
      3a. Seriously, not depending on file extensions will make handling image files with multiple data streams easier in the near future. Real digital cameras can output single files with JPEG, TIFF and RAW data.
      I totally don't understand this statement. You can mis-name the extension of a file in Gimp (or even not give it one at all) and it will automatically sort out what the file is by type, just as most unixy programs do. It works no matter what. In Windows, however, file extensions are and were the main way to determine file type. AFAIK, it continues the tradition to this day.
    39. Re:GUI perhaps? by Hakubi_Washu · · Score: 2, Interesting

      > Yeah the interface sucks
      I doesn't suck more than the Adobe interface. The definition of "suckiness" always seems biased away from the UI you're used to. I learned GIMP first and didn't have much trouble, but now I can't stand the crammed look of Adobe Apps, other people have it the other way round, and, fankly, I'm tired of people including "Yeah the interface sucks" just because.

      > I have to have an entire virtual desktop reserved for it alone
      I have always considered that to be the point of virtual desktops...

      > there are dialogs that pop up behind the window
      file or vote for a bug report if you consider this disturbing.

      > I have to spend more time resizing windows than actually working
      Use keyboard shortcuts instead of the mouse.

      > if you have a lot of images open the taskbar groups them so that it takes two clicks to get to anything
      if you have too many tabs open they're scrolled (I bet they are, but I don't have Adobe to check). Point is: use keyboard shortcuts instead of the mouse...

      > Why not have a nice tabbed interface?
      Why have one? Just to look'n'feel like Adobe? I am not interested in that (and I'm not interested in bringing the Adobe crowd "over" as well, why would I?)

      > Also the name sucks. At best its confusing, at worst its offensive.
      "GNU Image Manipulation Program" isn't more confusing than something reminiscent of a camera repair shop, just another case of biased perspective. And, as a BDSM person, I get a chuckle out of the abbreviation, too :-)

      > Its pretty sad when its obvious to everyone what the problem is, yet its still the same thing after what, six years?
      Maybe, after six years, you could accept that, apparently, it is NOT an obvious problem to a majority of people spending time on improving GIMP? It was never a problem for me, certainly, and I usually fail to see how it can even be one (I've also never accepted "People can't use OOo, because it's different from Word", every new version of Word shows this is a bullshit argument).

      What I can accept as a problem is lacking 16-bit and CMYK support, but only because I don't know enough about professional photo editing to know whether this has any merit. But then, how many people using PS are actually professionals? All my needs, from webdesign, over improving holidays snapshots and making skins for shooters, to preparing imagery for publications, have always been more than fulfilled by the GIMP and then some.

    40. Re:GUI perhaps? by Daengbo · · Score: 1

      Oh god! I can't believe that I wrote "it's." I'm going to kill myself.

    41. Re:GUI perhaps? by Farmer+Tim · · Score: 1

      I was pointing out the absurdity of the GPP not being able to find the command in Photoshop; its even more absurd, since its in exactly the same place in GIMP. Thanks for mentioning that...I like a good laugh.

      --
      Blank until /. makes another boneheaded UI decision.
    42. 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.

    43. Re:GUI perhaps? by Compuser · · Score: 1

      A program which is a world in itself should take care
      of everything. For instance, emacs has its own memory
      management - it does not entirely trust the OS. Guess
      what a tool that is the center of the user's
      world should do: it's own window management - relying
      on some other graphical layer is a shitty solution.
      If you assume that a tool is so important that people
      will buy computers just to run that one tool, then
      the tool must do everything to make the user more
      productive. You wouldn't buy a major database without
      native storage management layer, so how could a tool
      requiring good GUI for productivity not provide an
      end-to-end GUI solution?

    44. Re:GUI perhaps? by Rallion · · Score: 1

      This argument makes me laugh a little.

      Have you ever tried to use GIMP while you also had four or five OTHER programs running at the same time? If I'm doing web design, I usually have at LEAST three other windows open just for that -- often more. Makes you really appreciate the MDI interface. Really. A lot. Just switch tasks ONCE and you know everything you need is right there, and things unrelated to editing images isn't.

    45. Re:GUI perhaps? by KiloByte · · Score: 1

      Have you ever tried to use GIMP while you also had four or five OTHER programs running at the same time?

      Well, you see, I try to constrain myself to only 10 desktops at a time, forcing myself to close something when I run out of them. I guess that this answers your question.

      Generally, any single desktop interface breaks once you have more than 5-6 windows.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    46. Re:GUI perhaps? by Anonymous Coward · · Score: 0

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

      Well, as someone else said, in their opinion, most users stay away from the GIMP. So there aren't any users (yeah) or if there are, they are developers too.

      If you're pissed off

      a) Pay someone to do the changes
      b) Do the changes yourself
      c) Don't use GIMP and STFU

      I find neither PS or GIMP useable, but then I don't grok art packages (even 3d modelling, though tech drawing is OK). They are both a POS from my point of view.

      However, if there are lots of people willing to move over to Linux or use GIMP "if only they had ...", then club together and get a bounty put together to get what you want. NB: if you want CMYK, usable CMYK pantones are patent/trade secret and are NOT ALLOWED TO BE USED by Adobe. They also successfully sued a commercial competitor about copying their look n feel, so if you want that copied, then you'll need to put your names in so that you can be found if Adobe want to sue GIMP.

    47. Re:GUI perhaps? by kyrre · · Score: 1

      Again this is a problem with the window manager in Microsoft Windows(R). Most other window managers support virtual desktops out of the box. I do developing and find virtual desktops a must to be productive. Virtual desktops are available for Windows through Microsoft PowerToys for Windows XP. I have never used it so I do not know if it is any good.

      However the topic of the article is not GIMP on Windows, it is GIMP for GNU/Linux. So I think that this is not a valid complaint.

    48. Re:GUI perhaps? by clawoo · · Score: 1

      i couldn't find a way to get photoshop to resize an image and preview what the image was going to look like.

      Image > Image Size. To preview you can do whatever you want: save a copy, save for web, print preview.

      Seriously, I'm a relatively recent 24/7 Linux user but I tried to use Gimp on Winnie as well for a pretty long time and I can only come to this conclusion: Gimp's interface is brain damaged, it lacks usability, it's not made for speed editing. No graphic designer will want to waste time looking for a function buried deep down in a weirdass menu.

      Ow, and has any of the Gimp makers ever tried to work with Gimp and a few other programs (say, two) in the same time. If they did I guess their fingers started bleeding, just try and you'll see why.

      I'd really want an open source tool I could work with which would resemble Photoshop's functionality, but there really are no options (no, GimpSHOP does not count either, it's just not fast and clean enough). Photoshop is just one of those rock solid, good software applications, and there's nothing anyone can do about it.

      --
      This is not your signature.
    49. Re:GUI perhaps? by karbonKid · · Score: 1

      Couldn't agree more - working with layer masks in photoshop, especially, is needlessly convoluted, and dont't get me started on the copy-and-paste. It always seems that photoshop is trying to stay one step ahead of you, the user, and usually fails miserably in predicting what you are about to do, carrying out an action you never wanted it to. I'm not saying GIMP is perfect, but I first used in 4 years ago, when I was 12 years old, and have found it to have the most intuitive, easy-to-learn and powerful interface of just about everything except Wings 3D

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

    51. Re:GUI perhaps? by jilles · · Score: 3, Insightful

      Actually you are quite right. The big problem in the linux community is that they are not really open to this kind of criticism. People have been saying for years that UI sucks and for years it has continued to suck.

      Lets face it, the GIMP UI is pretty bad. It is going to take some major rearchitecting to fix that. One reason why that won't happen is that the people who are supposed to do that obviously don't get it (just look at the current UI ...).

      --

      Jilles
    52. Re:GUI perhaps? by uhmmmm · · Score: 1

      I did, and I sure don't recall that menu item existing in the context menu.

    53. Re:GUI perhaps? by uhmmmm · · Score: 1
      The point about it being a more powerful operation aside, it still takes my longer to find.

      Why? Because it's in the menus, and not in the context menu for the layers palette. The menus in Photoshop (and GIMP) have way too many items, so it takes too long to read through them if you don't already know where the one you want is.

      When the item is in the context menu for whatever part of the interface it naturally makes sense for, it suddenly becomes so much easier to find. Most basic layer operations are done withing the layers palette, so it makes sense to have that operation easily accessible through the context menu. That's not guessing where something it, that's logically grouping of like functionality.

      Either it isn't there in Photoshop, or I missed it somehow.

    54. Re:GUI perhaps? by travail_jgd · · Score: 1

      I agree 100%. Although I'm not offended by the "gimp" name, it's hard to take it seriously after watching Pulp Fiction.

      The worst part is that someone tried to fix the Gimp interface, but was told to keep his changes to himself. (It's been posted and duped on Slasdot as well.)

    55. Re:GUI perhaps? by Anonymous Coward · · Score: 0
      I think it's a little unseemly to bash people who give you something for free.

      I think people bash it because they feel they've been lied to. Fanatics tell people that the gimp is as good as photoshop, and that gets people's hopes up. When they find out that it's a weird tool that only makes sense to unixey code freaks they get disappointed, and that's when they start complaining. If the line was more along the lines of 'well it's different to photoshop; give it a try, maybe you'll like it, maybe you won't', I'm sure people would be a lot more forgiving.

      As for getting involved in the community; the developers don't need non-coders to join some mailing list when the message is perfectly clear: The UI is weird. It's different to everything we're used to. It doesn't feel nice. There's a zillion little windows and they all get lost behind each other. Make it a bit more like every other paint program and people will know WTF is going on.

    56. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      A Gimp is also:

      A homosexual sex slave

      OR

      A Paladin from World of Warcraft.

    57. Re:GUI perhaps? by Hosiah · · Score: 0, Troll
      And yet a style that is retained in every serious image editor*... but nooo, the GIMP people are right and everybody else is wrong.

      You mean like the serious image editors in the screen shots in this article? Or are movie studios not "serious"?

      No, I could care less about your karma. It's clear, for whatever reasons, that you're committed to screaming down all FOSS no matter what. Dime a dozen...

    58. Re:GUI perhaps? by grantsellis · · Score: 1

      Actually, Photoshop on Mac uses a SDI, similar to GIMPs, unlike the MDI it uses in Windows.

      The difference? Photoshop automatically checks to make sure graphics windows aren't covered by your pallette setup. (Illustrator, on the other hand, always creates documents under your pallettes, like GIMP).

      (I use Photoshop in Windows and Mac.)

    59. Re:GUI perhaps? by Gulthek · · Score: 1

      Why have one? Just to look'n'feel like Adobe? I am not interested in that (and I'm not interested in bringing the Adobe crowd "over" as well, why would I?)

      Because if there's one thing OSS does well, it's providing lots of options for the user.

    60. Re:GUI perhaps? by Haeleth · · Score: 1

      You see, this is the great thing about MDI interfaces - if you maximise them, they act almost like virtual desktops! Except you can also resize them and move them around. And the "desktop" for an application is created automatically when you launch the application, and closed automatically when you close it - so you don't have to manage things by hand, and you don't have to worry about the case where you have N virtual desktops configured and N+1 applications you want to run. Which all makes it actually rather more convenient than virtual desktops, for some people.

      Incidentally, I find it kind of amusing that many of the people who praise GIMP for its multiwindow design also tend to praise Firefox for its tabbed browsing. Why is it good to have MDI in Firefox, but bad to have MDI in GIMP?

    61. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      Ctrl-E. Wow, that was so difficult.

      No, pressing Ctrl+E is not difficult... but intuitavely discovering that, given GIMP's interface, is.


      If the only complain left about the GIMP's interface is that it makes it hard to discover how to merge layers in Photoshop, I'd say it's one of the best interfaces we have.

    62. Re:GUI perhaps? by Hakubi_Washu · · Score: 1

      > Because if there's one thing OSS does well, it's providing lots of options for the user Bzzzt, wrong. The Option is to a) use a fork/plugin/etc, (I don't know whether Gimpshop does this), b) develop such a thing, c) use a different app or d) code optional support into Gimp (though this'll make it bloated). Notice how "swap the UI to a tabbed one" is not one of the options? You CAN have the option, but I asked why one would NEED to have this specific one.

    63. Re:GUI perhaps? by plumby · · Score: 3, Insightful
      "Its pretty sad when its obvious to everyone what the problem is, yet its still the same thing after what, six years?"

      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

      You're possibly right, but I guess it's a pretty major problem for a lot of non-users. I bet a fair few potential users will have loaded it up, gone 'WTF' and gone back to their previous image editing tool of choice. I know I did.

      Much as I support the idea of a powerful, free graphics package, I really could not be bothered with trying to get past (in my view) one of the most user-unfriendly UIs that I've seen for a very long time. I also couldn't be bothered to go and code my own amended UI (I want to edit images, not develop the tool) or go start harassing the actual dev community, who would quite likely come back with either "Well, we like it" or "Well, go write your own".

      At the end of the day, I'm happy enough with Photoshop Elements for most of what I want to achieve, and therefore can't be bothered to spend any significant time trying to make GIMP better (if it were improved, I may well go back and give it another go, however).

      My suggestion to all the people bitching about how GIMP sucks and how much they hate using it (why are you using it then?) is to become a part of the community. Contribute and if enough of you contribute enough then your needs will probably be taken care of too. Failing that you could always take up a collection and offer a bounty.

      And this is exactly the sort of response that I'm talking about. I am interested in a decent, usable graphics editor. I don't really care what that tool is. I am not bitching about the UI, and saying that it should be changed. I simply care that the graphics tool that I use has a UI that I can get on with. GIMP doesn't, so I don't use it. I don't actually care enough about GIMP as a project to spend valuable time working to improve it. If that means I will never get a decent free graphics app, and instead have to stump up £50 or whatever to get Photoshop Elements, then so be it.

      I think it's a little unseemly to bash people who give you something for free. If you don't like it you are under no obligation to use it. Just steal photoshop like everybody else at /. does.

      And yet you're bashing someone who's giving you advice for free. As you say - if you don't like it, your're under no obligation to use it. But if you're actually interested in creating a tool that people will use, not because it's free, but because it's better, then you might want to consider the views of the people that don't currently use it.

      And don't try to take the stance that the only choice is GIMP or theft. As I've said, I use (and have bought) Photoshop Elements (I've also bought the ACDSee suite, but decided that Photoshop was better, I would have been happy to use - even pay for - GIMP had been been usable enough for me).

    64. Re:GUI perhaps? by Hosiah · · Score: 2, Insightful
      Those in charge of the GIMP dismiss such experienced users in the field as feeble-minded ignoramuses.

      OK, I'll bite. Do you have a link to someplace where a Gimp developer dismisses experienced users in the manner in which you speak? By the way, I already refuted the TFA's ludicrous claims yesterday Mainly because as soon as I saw an anti-Gimp FUD hack job, I knew it was a sure bet it'd get posted to /.

      I say again, I'd be only too happy to see Photoshop ported. Perhaps the Adobe people will see the demand and cave. But hating Gimp for reasons mentioned in TFA is like saying you don't like cars because they lack steering wheels, tires, and motors.

    65. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      Have you ever tried to use GIMP while you also had four or five OTHER programs running at the same time?

      Yes, and I have also tried the same things with MDI programs like SQL Query Analyzer (forgive the example, I don't own Photoshop, and as a Linux user, I'm against "piracy"). And one thing that is really great about Gimp, that I hate about every MDI interface is that I can put the windows in the order I want them. E.g. I can put the image window above firefox, which is above the toolbox, when I need that.

      With an MDI program, I'm stuck with having every freaking window on top, because of the stupid container, and it's only really usable when maximizided, so it's like using good old MS-DOS 3.3 - only one program visible at a time.

      Obviously, graphics artists have the same problem, because every one of them has at least two screens to solve the problem of Photoshop with it's Windows 3.1 interface covering everything else. You can't do web stuff without at least one browser, and with an MDI container covering everything else, a second screen is really needed for the browser.

    66. Re:GUI perhaps? by MidnightBrewer · · Score: 3, Informative

      a) Pay someone to do the changes

      Kind of misses the point of free software. When you say, "it's free, so stop your bitching," what you're really saying is "you get what you pay for, and you're better off paying for it." How does that make open source software better again?

      b) Do the changes yourself

      Not everybody is a programmer. This is the first excuse that a lot of people run for, and it's weak. The whole point of an "open-source community" is the idea of people exchanging ideas to create really useful software for everybody. End users's opinions shouldn't be shot down just because they're not programmers. Even real programmers might have good opinions but just not enough spare time in their day to dive into the cruft of somebody else's buggy code and start making it better.

      One of the biggest complaints of the guy who cobbled together GimpShop was that all the resources were scattered around with no rhyme or reason, making tracking things down really hard to do. If a programmer came in and fixed all that, who's to guarantee that the maintainers will buy it? There are egos involved, not to mention a "community;" one person can't fix everybody else's mistakes at one go.

      c) Don't use GIMP and STFU

      Yep, that's a sure-fire way to make the Gimp better. "Sure, our program sucks, but you don't have to use it." Might as well pack it in and call it quits with that kind of attitude. What's the point of creating software if people don't want to use it? Why even make it public it if you're not prepared to hear what the rest of the world hears about it?

      What we're talking about is the large majority of serious Photoshop users, not just one or two malcontents. I think it would be cool if the Gimp competed. There are just a few basics that could be implemented that would make some serious waves in Gimp adoption, without turning the Gimp into some sort of bastardized Photoshop clone.

      --
      "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life
    67. Re:GUI perhaps? by slavemowgli · · Score: 2, Insightful

      This is so typical of what is wrong with the open source movement.

      No, no, no! That's a typical example of what's wrong with some people, but it isn't fair to decry all of the "open source movement" (itself a misleading term, BTW, since there is no single, coherent movement) just because of some comment some random schmuck makes on Slashdot. Really, before making comments like that, just try substituting something else for "open source movement" first - "closed source movement", for example -, and if the whole thing doesn't make sense anymore then, then it probably didn't before, either. :)

      That being said, the rest of your comment was very insightful, so thanks for that.

      --
      quidquid latine dictum sit altum videtur.
    68. Re:GUI perhaps? by labratuk · · Score: 1
      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.

      Nice the way you make it sound like you do have the opportunity to make decisions about the direction of proprietary software. I take it you're on the Adobe UI Review board, then?

      I know Photoshop stopped going in the direction I wanted it to go after about version 4.0.
      --
      Malike Bamiyi wanted my assistance.
    69. Re:GUI perhaps? by Magic5Ball · · Score: 1

      Perhaps I just keep hitting bad betas that are broken on Windows and Mac and Linux, but I've never been able to point GIMP at convert'ed xwd or print screen files (PNG) without extensions and have it just work. Unknown file type or signal 11 are the usual results. Renaming the files to include an extension allows the files to open, so I can only assume that something in the GIMP is relying on the file extension for opening the file or determining its file type.

      On your second point, digital image manipulation was not a domain of Windows until about 10 years ago. Image editors on every other platform have used the file headers to determine file type for much longer than that.

      --
      There are 1.1... kinds of people.
    70. Re:GUI perhaps? by Jack9 · · Score: 1

      The definition of "suckiness" always seems biased away from the UI you're used to

      And in some cases it's just poor design. Cntrl-K for delete instead of say, the delete key. Welcom to a GIMPed GUI

      --

      Often wrong but never in doubt.
      I am Jack9.
      Everyone knows me.
    71. Re:GUI perhaps? by maxwell+demon · · Score: 1
      Kind of misses the point of free software. When you say, "it's free, so stop your bitching," what you're really saying is "you get what you pay for, and you're better off paying for it." How does that make open source software better again?

      For a proprietary program, you are at the mercy of the original supplier. If you badly need a feature in Photoshop, and Adobe just tells you they won't implement it, then you're out of luck.
      For an open source program, if the original supplier won't implement your feature, you can still go to any programmer with the needed abilities who is willing to write that stuff (be it for free or, more likely, for payment). And as soon as it exists, you may even be able to get it into the official program (that's assuming the rejection was on too-much-work grounds, not on rejection based on the feature; but even then, an existing, successful feature may change the primary developers' minds).

      Also, it's much more future-proof. If Adobe some day decided to stop Photoshop development, you wouldn't have any chance to get a replacement. OTOH with open source, there's still the possibility to find new maintainers for the program (or for a business which depends strongly enough on it, even to hire some programmers to maintain it). In short, you cannot withdraw open source.
      --
      The Tao of math: The numbers you can count are not the real numbers.
    72. Re:GUI perhaps? by Farmer+Tim · · Score: 1

      The contextual menu is there in Photoshop, either as a right click or from the widget on the palette (granted, it is easy to miss).

      I agree that the menus in both programs are overcrowded, though I don't have any problem scanning long lists; maybe I'm just too used to Apple's Human Interface Guidelines*, and the principle that any command available through a contextual menu should appear in another menu available to a single button mouse.

      Perhaps a GIMP-lite (KiddieGIMP?) interface option that hides the more complex or technical features might be a good way of introducing it to people without the Photoshop baggage (though that would spark a new debate over which are the critical basic features...).

      Truth be told, the similarities between the two programs are greater than the differences; that might be part of the problem (they're deceptively close in some ways, but different enough to be annoying). And what it really boils down to is you're using the tool that suits you with the features you want, so there's really no point in disputing which is "better", we're really just beating each other with opinions that are equally valid. In my case, I actually need 16 bit colour, CMYK and Pantone, so that rules out GIMP as anything but an experiment.

      *Admitting I like Photoshop and use Macintoshes...I'm going to earn some foes tonight.

      --
      Blank until /. makes another boneheaded UI decision.
    73. Re:GUI perhaps? by Shelled · · Score: 1
      "Go ahead, GIMP-fans, do your worst to my karma - I have plenty.

      What a laugh, anyone with experience watching the usual Slashdot Gimp-slamfest knows that has a much chance as a winter rain of toads. Lets compare Gimp with the most used sotware on the planet, MS Office. Context sensitive menu right click? No, Gimp and Office. Context sensitive pull down. No again. Tab box? Gimp developers are to force what everyone deems sensible, or just you? I find them fine, it takes a second or two to change and the setting holds across session. Less than a minute to set your preference for the life of the software, how does this make it the "Worst...Interface...Ever" again? You were shown to be wrong on the floating toolbar, it can be skipped. And I love this line from someone defending software using a GUI completely different than the standard operating paradigm for the last ten years:"...and everybody else is wrong."

      Including Office, the software you used to type your post, and pretty much every other piece of Windows software written this century are 'wrong'? Photoshop zealots as a class would probably say 'yes'. There's a stronger case to be made that Adobe has has held back GUI development in the photo ediitng field by training an entire generation of workers in a dead GUI style. You don't read audio professionals beratng every editing package not identical to Protools as the "Worst...Interface...Ever", nor engineers do same to users of alternate Spice packages, or in pretty much any other professional field do you see the same kind of ossified elitism that common in the photo editing field. But then again, "...everybody else is wrong."

    74. Re:GUI perhaps? by Hatta · · Score: 1

      Incidentally, I find it kind of amusing that many of the people who praise GIMP for its multiwindow design also tend to praise Firefox for its tabbed browsing. Why is it good to have MDI in Firefox, but bad to have MDI in GIMP?

      The ideal situation is to have both. Menus, windows, tabs, etc should all be attachable and detachable at will.

      --
      Give me Classic Slashdot or give me death!
    75. Re:GUI perhaps? by smellsofbikes · · Score: 1

      >>Its pretty sad when its obvious to everyone what the problem is, yet its still the same thing after what, six years?
      >Maybe, after six years, you could accept that, apparently, it is NOT an obvious problem to a majority of people spending time on improving GIMP?

      I don't know about the people spending time on improving GIMP. I do know that *every* *single* *person* I have tried to convert to GIMP, including myself, dislikes the interface with stunning intensity. The only thing keeping about eight people I know from going linux only is Adobe Photoshop.

      --
      Nostalgia's not what it used to be.
    76. Re:GUI perhaps? by marcosdumay · · Score: 1

      That would be a nice plus at a desktop environment.

    77. Re:GUI perhaps? by Anonymous Coward · · Score: 0

      I think that your post underscores one of the critical downfalls/shortcomings of the open source movement.

      We are getting to the point where the end users of the software are very different than the designers and coders.

      The skill sets are so different. How does a graphic artist get involved in the project to make the GIMP better when they have no coding experience, and their skills are so different than the types of persons needed to develop the project.

      It was/is a piece of cake on stuff like Linux, as the geeks who code are the ones who know how an operating system should work. The problem is with the GIMP and even OO.org is that the users of the system are different than the people designing it.

      Open source needs to encourage people to get involved at the many many different roles. This I think is the critical challenge of open source as it matures and moves into areas of software with a less geek focus.

    78. Re:GUI perhaps? by marcosdumay · · Score: 1

      "The definition of "suckiness" always seems biased away from the UI you're used to."

      Funny, I have being collecting some "interface measurement dimensions" for a time. Let's see what it does...

      Concision: Multi window reduce that on GIMP tools, when compared with Photoshop. GIMP menus are also many times several steps bigger, but Photoshop have some other complications, so I think they match on menus.

      Expressiveness: Both do nearly the same.

      Ease (mnemonic load): Remembering what window you are working (and what is under it) increases mnemonic load. GIMP loses.

      Transparency: If I remember it well, Photoshop transformations have preview. If so, they match.

      Discoverability: Photoshop's single window is normal. GIMP's multiple windows are new. Photoshop wins that. Also, Photoshop's menus are better organized.

      Scriptability: Both are very bad on that.

      Memorability (if users forget it when don't use): The only thing to forget is the menus order. GIMP loses on that.

      Errors: If I remember Photoshop well, GIMP wins by far on error messaging and recovering. The undo window is excelent.

      Satisfaction: Very subjective. I prefer not to opine.

      "> Why not have a nice tabbed interface?
      Why have one? Just to look'n'feel like Adobe?"

      You know? There is a reason that all those programs are using tabbed interfaces...

      "Point is: use keyboard shortcuts instead of the mouse..."

      It is an image manipulatin program. Why do you think that using the keyboard is reasonable?

    79. Re:GUI perhaps? by Hakubi_Washu · · Score: 1

      > Funny, I have being collecting some "interface measurement dimensions" for a time. Let's see what it does... You have... > Concision: Multi window reduce that on GIMP tools, when compared with Photoshop. GIMP menus are also many times several steps bigger, but Photoshop have some other complications, so I think they match on menus. I consider PS crammed, but suit yourself. > Expressiveness: Both do nearly the same. Whatever you mean by that. > Ease (mnemonic load): Remembering what window you are working (and what is under it) increases mnemonic load. GIMP loses. Windows, Tabs, doesn't change a thing, sorry. > Transparency: If I remember it well, Photoshop transformations have preview. If so, they match. Gimp has previews for most effects and yes, they match, too. Your point? > Discoverability: Photoshop's single window is normal. GIMP's multiple windows are new. Photoshop wins that. Also, Photoshop's menus are better organized. New to the Windows user maybe, but hardly in general. > Scriptability: Both are very bad on that. I don't know about PS, but the Gimp is pretty easy to script, although I would prefer something imperative over the functional style. > Memorability (if users forget it when don't use): The only thing to forget is the menus order. GIMP loses on that. Hm, got a memory problem? I don't tend to forget such things, but then, maybe, as a coder I'm more susceptible to underlying structures than most people? > Errors: If I remember Photoshop well, GIMP wins by far on error messaging and recovering. The undo window is excelent. Can't compare PS, but Gimps error messages are just as hard or easy to read as any other coder-type apps... Which mean I constantly hear people complaining. > Satisfaction: Very subjective. I prefer not to opine. That is exactly the point I was trying to make, wasn't I? > You know? There is a reason that all those programs are using tabbed interfaces... That is not necessarily because "it's better", it could as well be because "everyone uses them". Be carefull here. Tabs are good for relatively static things, like text windows, but I strongly prefer to place different images next to each other when editing, since they're usually related some way. > It is an image manipulatin program. Why do you think that using the keyboard is reasonable? It's a computer programm. Why do you think something reminiscent of a piece of soap is better suited to images?

    80. Re:GUI perhaps? by Watts+Martin · · Score: 1

      Photoshop has a complete object model exposed to scripting languages, and is scriptable in Javascript (on Mac and Windows), AppleScript (Mac only) and VBScript (Windows only); technically, it's scriptable in anything that can send Apple Events on the Mac or OLE commands on Windows. It's not uncommon to hear about sophisticated workflows people have put together -- coordinating Photoshop actions, OS features and even other applications -- using AppleScript. Photoshop's scripting capability is often cited by professionals as one of its best features.

      No offense, but writing that off blithely as "pretty bad scripting" casts a bit of a shadow over the rest of your analysis for me.

    81. Re:GUI perhaps? by FooBarWidget · · Score: 1

      "I haven't tried Gimp on Mac to know how out-of-place it's file selector is there." ......
      Dude, the GTK file selector looks almost identical to the MacOS X file selector!
      How come people complain at the GTK file selector, but praise the Mac file selector, when they're almost identical?

    82. Re:GUI perhaps? by FooBarWidget · · Score: 1
      Though yeah, the GTK has a horrific file selection browser that's supposedly designed to be "user friendly"


      Is MacOS X friendly? You'd probably say yes. Is the MacOS X file selector friendly? You'd probably say yes. Well here's a surprise for you: the GTK file selector is almost identical to the MacOS X file selector. Then how come the GTK file selector is bad and the MacOS X file selector is good? Please, do explain this. The only reason I can come up with is that people these days like to bash Linux-based stuff and like to praise OS X, even when they've never used the latter.
    83. Re:GUI perhaps? by Short+Circuit · · Score: 1

      And three years from now, GIMP will still be free, while Photoshop will still cost more than a new low-end computer.

      Forget what "those in charge of" something think. In the Open Source world, if enough people don't like something, it gets forked and fixed. I believe someone even rewrote the GIMP UI to look like Photoshop...but nobody uses it.

      Oh, about your "Most dual-users find Photoshop's UI vastly superior" comment. No, I won't ask for numbers, you don't have any. I want to know how in heck you could expect to come up with an unbiased survey.

      I find Both GNOME and KDE's interfaces to be superior to Windows XP. Does that mean there are more users of those two desktop systems than of Windows XP? No. But I bet if MS Paint was replaced with the GIMP, or Elements downloads appeared right next to GIMP downloads in most places, you'd see a shift in attitude.

    84. Re:GUI perhaps? by Mad+Merlin · · Score: 1
      Perhaps I just keep hitting bad betas that are broken on Windows and Mac and Linux, but I've never been able to point GIMP at convert'ed xwd or print screen files (PNG) without extensions and have it just work. Unknown file type or signal 11 are the usual results. Renaming the files to include an extension allows the files to open, so I can only assume that something in the GIMP is relying on the file extension for opening the file or determining its file type.

      Just copied a png file to foo (no extension), opened foo in GIMP and it recognized it as a png and loaded it correctly. Not sure what an xwd file is, otherwise I'd try that too.

    85. Re:GUI perhaps? by howlingmadhowie · · Score: 1

      sorry, i used the wrong word, i meant crop, not resize. gimp has a nice feature, that you can drag the picture you want to crop around in the crop window, so you can see what it will look like. i couldn't find a way to do this on the (admittedly very cheap) version of adobe i was using.

      personally i don't have any problems with gimp, maybe because i don't have to do that much with it. all i use it for is correcting photos of an oscilloscope display (getting the perspective right, cropping the image, inverting colours, changing contrast and brightness) so i'm probably not the best person to talk about either photoshop or gimp.

      i would say this though. the people who develop gimp know a lot about the software (and presumably something about the competition and the work people tend to do with the software). they have chosen this layout above the layout used by photoshop. the question you should be asking is, why?

      howie

    86. Re:GUI perhaps? by arose · · Score: 1
      Kind of misses the point of free software.
      Yes, you do.
      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    87. Re:GUI perhaps? by TekPolitik · · Score: 1
      It's clear, for whatever reasons, that you're committed to screaming down all FOSS no matter what.

      You could not possibly be more wrong.

      GIMP is not all FOSS. It is one app that just has an appalling user interface.

    88. Re:GUI perhaps? by killjoe · · Score: 1

      I have lost a lot of karma for defending GIMP but here it goes anyway.

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

      MS has kept things crummy for six years but that's beside the point. This is not a "product". GIMP is not run by a corporation.

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

      Well sorry but that's the way open source works. The project is responsive to it's community. If you refuse to join the community how can you expect it be responsive to you? Sorry but that's the say it is.

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

      The TFA is about that, all the /. comments are nothing but bashing the GIMP developers for not giving them a free version of photoshop.

      "It doesn't make sense to be oblivious to real user needs and, simultaneously, to bash real users for not using specific stuff."

      Who is bashing the users for not using GIMP?

      "I know I'm Captain Obvious for spelling this out, but it seems to be needed."

      Point to me to a few articles bashing people for not using GIMP, until then you are merely full of shit. People who don't use GIMP are the ones bashing it. This doesn't make sense to me. If you don't like then use photoshop and be happy.

      --
      evil is as evil does
    89. Re:GUI perhaps? by killjoe · · Score: 1

      "Finally, good usability requires huge amounts of humility."

      No, good usability requires a tremendous amount of work. So the question is who is going to do the work, why, and how?

      Since you are not willing to do the work, who is? And are those people going to be more motivated to make you happy while you are shitting on them or while you are helping them?

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

      MS has humility? Since when?

      --
      evil is as evil does
    90. Re:GUI perhaps? by killjoe · · Score: 1

      "Kind of misses the point of free software. "

      Yup, you missed the point entirely.

      "Not everybody is a programmer. This is the first excuse that a lot of people run for, and it's weak."

      Nope. But then again you don't have to be one to contribute.

      "The whole point of an "open-source community" is the idea of people exchanging ideas to create really useful software for everybody."

      No the whole point of the open source community is that everybody pitches in to create really useful software. Exchanging ideas is just a tiny part of that. The hard work is coding, helping users, contributing to the listserve, writing documents, debugging, testing, etc.

      The problem is that people like you want to do nothing but want other people to create a clone of photoshop and give it to you for free. Worse yet you want to shit on them the whole time because they are not working fast enough or that what they create isn't good enough for you. If you are not willing the help the least you can do is not to shit on the people doing the work.

      "One of the biggest complaints of the guy who cobbled together GimpShop was that all the resources were scattered around with no rhyme or reason, making tracking things down really hard to do."

      Well there you go. You just found a defect in the system where you can help. Go to it.

      "Yep, that's a sure-fire way to make the Gimp better. "Sure, our program sucks, but you don't have to use it.""

      Who says it sucks? You? Maybe the some people think it's great.

      "Might as well pack it in and call it quits with that kind of attitude."

      It's better then "you guys suck, your software sucks, I don't use your program but I am going to tell everybody how much you suck and how much your software sucks. Photoshop is better, open source sucks. Hurry up and make your program exactly the same as photoshop so I can have a free copy of photoshop".

      I'd say your attitude sucks way more.

      "What we're talking about is the large majority of serious Photoshop users, not just one or two malcontents."

      Large majority of photoshop users are people who pirated it and use to it touch up pictures. The people who pay for it are pros using macs they will never switch to linux and gimp.

      "here are just a few basics that could be implemented that would make some serious waves in Gimp adoption, without turning the Gimp into some sort of bastardized Photoshop clone."

      Well then keep shitting on the developers and the community, maybe they will get tired of you bitching at them and give you what you want.

      --
      evil is as evil does
    91. Re:GUI perhaps? by strider44 · · Score: 1

      I doubt it's exactly the same - I mean it doesn't look the same from my end looking at your picture, though I say this without having used Mac OSX enough to remember the file selector! The main complaint with the GTK file selecter is that for some inane reason you can't manually type in the filename in the load file dialogue. Sometimes the GTK group make some absolutely idiotic decisions in the name of "user friendliness" where "user friendliness" seems to be equivalent in their minds to "taking out all of the features" (Not too long ago Linus Torvalds did a nice flame on this topic). So what then happens when you have a thousand pictures simply named 1.jpg to 1000.jpg and you want 346.jpg? With this file selector you literally cannot just type in 346.jpg, you must use the list to select it. From what I hear Mac OSX, though it's user friendly, still tries to be powerful as well, and admittedly I'm just assuming if they did something so idiotic as this people would be saying something about it.

    92. Re:GUI perhaps? by Stu+Charlton · · Score: 1

      And three years from now, GIMP will still be free, while Photoshop will still cost more than a new low-end computer.


      If its free, but it sucks, is it really free?

      In the Open Source world, if enough people don't like something, it gets forked and fixed.

      Ah, but In the real world, most software consumers are not also software producers. If people don't like something, they switch to a competitor's product. Hence why Photoshop will still cost as much as it does until a group with enough incentive decides to seriously take them on.

      --
      -Stu
    93. Re:GUI perhaps? by Short+Circuit · · Score: 1

      If its free, but it sucks, is it really free?

      I won't argue against flagrant bias.

      Ah, but In the real world, most software consumers are not also software producers. If people don't like something, they switch to a competitor's product. Hence why Photoshop will still cost as much as it does until a group with enough incentive decides to seriously take them on.

      Free Software exists in the real world. You don't need most people to be simultaneously software consumers and producers...you only need just enough of them to get the software fixed and/or forked. Tack on a new name (Like, say, "Ubuntu", "Phoenix/Firebird/Firefox", "Perl" or even "CentOS"), and the laypersons memory of the bad version of the product isn't associated with the new codebase.

      Suddenly, the consumer sees another competing product, but this one's free. So they give the "new guy" a try. That's the beauty of this whole FL/OSS movement.

      (I mention Perl above, because it's a derivative of awk...and has greatly exceeded awk's usefulness and popularity.)

    94. Re:GUI perhaps? by NetRAVEN5000 · · Score: 1
      I think this is one of the biggest problems with people criticizing open-source.

      You misunderstand us, my friend. It's only a select few of us who want to make "users switch from MS to free stuff". We don't care what you use, we just want people to realize that there are other options.

      Too many people bitch and moan about how much MS software freezes and other things, and so we tell them that Linux is more stable (because, at least in my experience, it is). Some people might complain about the graphics tools that come with Windows and Office, and so we tell them about GIMP (which, undeniably, is MUCH more powerful than anything that comes with Windows or Office). People get pissed at IE for all its problems, we point them to Firefox or Mozilla.

      Not that we want these people to switch if what they're using works for them, but we don't want to have to listen to their bitching and complaining about how IE sucks, how they hate having to reformat Windows, how WinXP and Office are so expensive, etc.

      I'm more than happy with The GIMP, but if you're willing to shell out an extra $600 or so for Photoshop (which appears to be its going price) just because it has CMYK, I have no problem with that - certainly that price tag is way too high for my liking, but I'm not buying it so that's not my problem. . .

      And as far as what you said about usability goes. . . we're programmers, not usability experts. MS and other software companies actually have experts that advise on how to make software easy to use. Many OS projects don't have that, and many never will.

      Why?

      "Usability isn't that difficult". Says you. Says me, and a million other programmers. Do you see the problem with this thinking? It's human nature. "Well it's easy for me to use." Of course, as a programmer, MY interface makes sense to me. It's never going to get fixed because the people who see it as a problem don't want to fix the code, and the people who are willing to fix the code don't see it as a problem.

    95. Re:GUI perhaps? by Magic5Ball · · Score: 1

      Scratch that. I found a new copy of Gimp 2.2 that yum-updated itself over the weekend at work, which seems to have fixed the issue. I can't wait to unleash it on my Appleshare network to see what else it can read now.

      xwd is a tool for obtaining screen dumps in X (and often the file extension for said dumps).

      --
      There are 1.1... kinds of people.
    96. Re:GUI perhaps? by FooBarWidget · · Score: 1

      I didn't say they're exactly the same, I said they're almost the same. Look at the layout.

      As for your comment: you can. The GTK list box supports type-as-you-find since 2.6, and the list box in the file selector is focused by default so you can immediately begin typing. For a comparison, look at the MacOS X open file dialog - it also doesn't have a filename entry, just like the GTK one!

    97. Re:GUI perhaps? by Imsdal · · Score: 1

      MS has kept things crummy for six years but that's beside the point.

      No, it's not. This was a comment to someone who suggested that if something had stayed in a certain way for six years that was because it was good enough as it was and there were no user demands to change it. I just pointed out that that was a silly argument.

      The project is responsive to it's community.

      Yes, that's my point exactly! And also the point of several others in this thread. In fact, I'm starting to think that a majority of /. posters agree on what I'm about to say here.

      Open Source projects are built by their communities, but they are also built *for* their communities. This is in very sharp contrast to traditional software companies. The software they build is built by them, but built for *users*. That makes a huge difference.

      Before you all go overboard about how crappy commercial software is, let me state that just because they build it for users, it doesn't follow that they are successful. However, some companies are. In particular, Microsoft are extremely successful with the Office Suite (in particular Excel), and Adobe are with Photoshop.

      The difference between developing for the community and developing for users is pretty profound. How do you measure success? How do you measure usability? How do you rate the importance of different feature sets? These questions are answered in wildly different ways by MS/Adobe on the one hand, and the Open Source community on the other hand.

      If one wants software to be used outside of the development community, that software will have to be developed in a different way. I'm not saying that is the way open source *should* go. I don't have any right to demand anything, since I don't contribute. But I can say that I personally would wish for them to go that way. And I can guarantee that if they want to spread their software outside of the community, they will have to do things differently.

      The TFA is about that, all the /. comments are nothing but bashing the GIMP developers for not giving them a free version of Photoshop.

      We agree about what TFA is about, then. The way I interpret the comments, they are not about "bashing". They are about usability issues with GIMP that makes it an impossible sell for PS users. I certainly see how that can be taken as bashing by someone wearing different glasses. But if you want GIMP to have a stronger presence outside of its current community, you will have to change your glasses.

        People who don't use GIMP are the ones bashing it. This doesn't make sense to me. If you don't like then use Photoshop and be happy.

      Thos who "bash" it are people who tried it but didn't like it. I guess a huge majority of those people are just like me. We would like to see free software blossom and we hope it will one day be very successful. But we have real work to do. Accordingly, we can't use software that is worse than what is currently best in class.

      Please note the difference, then, between using PS instead of GIMP (out of a necessity) and being happy about it (which doesn't follow).

      Everyone who is in the community will have to ask themselves this question: Do I want this software to be used outside of the community? If the answer is no, then please don't post stupid comments about why everyone in the world is a moron for using M$ products. (You don't think those comments exist? Try reading /. comments. You'll be surprised...)

      If the answer is yes, you will have to realise that *you* will have to change how the software is developed. Asking for users to change is wrong on so many levels.

    98. Re:GUI perhaps? by Imsdal · · Score: 1

      Nice the way you make it sound like you do have the opportunity to make decisions about the direction of proprietary software. I take it you're on the Adobe UI Review board, then?
      Of course not. If I can't find the time to be a part of the community for application x, I can't find the time for giving input to the commercial application y either. Yet, strangely, further development of y is, in my experience, much more likely to be positive for me than for x. The reason is that the company that develops y has very strong incentives to add stuff that makes sense to typical users, and more often than not, I am a typical user.
      I know Photoshop stopped going in the direction I wanted it to go after about version 4.0.
      That's sad to hear. I don't use it, so I can't comment, but I do know that Excel, MS SQL Server, BusinessObjects and UltraEdit, which are the four applications I use the most, have improved incredibly much in the ten years I have used them (shorter for UltraEdit. I don't even know if that has been around ten years.)

    99. Re:GUI perhaps? by Daengbo · · Score: 1

      For what its worth, my copy of SAMS Gimp in 24 hours, which is based on Gimp1.0 and published in 1999, mentions on page 23 (in "A Word about Unix and File Format Extensions") says "So if ... you have a GIF file named picture.jpg, you can still easily open it in GIMP. ... It does this more or less by looking at the file data itself, not at the filename." I think that you were just jacked up somewhere in the past, because GIMP has been that way for as long as I've been using Linux (c.1997?).

    100. Re:GUI perhaps? by Stu+Charlton · · Score: 1

      I don't think you read my point.

      what I said: Photoshop will still cost as much as it does until a group with enough incentive decides to seriously take them on.

      what you said: you only need just enough of them to get the software fixed and/or forked.

      Sounds similar. Our disagreement is one of incentives -- I don't think there's been a fork of GIMP because there are going to be only two broad incentives to do so: a group of volunteers that don't like GIMP and want something better, or a group of people that want to make money by killing Photoshop. Generally speaking, neither has happened.

      The following point to me is rather bizarre:

      Suddenly, the consumer sees another competing product, but this one's free. So they give the "new guy" a try. That's the beauty of this whole FL/OSS movement.

      That has nothing to do with FL/OSS, that's the way MARKETS work -- whether the code is freed or not has nothing to do with whether a competitor exists and/or is cheaper.

      Ok, so forking a codebase in theory makes the costs associated with creating a competitor product lower, but one would have to wonder how radical the difference between is if it doesn't require a ground-up rethink. Perl, for example, may be a conceptual derivative of awk, but I don't recall it being a fork. Again, this has nothing to do with the availability of the source -- it's just a software marketplace at work.

      --
      -Stu
  4. Gimp Isnt enough. by SirDrinksAlot · · Score: 0

    Gimp isnt enough. PERIOD. No matter how much people want to think it is, it's no where near Photoshop. Just because you can reorganize its menu options to look like photoshop its not photoshop!

    Gimp is NOT for professionals.

    1. Re:Gimp Isnt enough. by starwed · · Score: 1

      Without giving reasons your just spouting hot air. I'm not a proffesional, nor have I ever used photoshop. To actually add to the debate, you should either give some reasons why the GIMP isn't good enough, or at least link to some site which does the same. (I'm sure they exist, given how often I've seen this type of comment.)

    2. Re:Gimp Isnt enough. by Eightyford · · Score: 1

      He said, PERIOD, so obviously there's nothing left to argue about. ;)

    3. Re:Gimp Isnt enough. by SirDrinksAlot · · Score: 1

      I'm tired of the argument, it's been beaten to death. I'm not going to bother going through the pages of things that The GIMP fails at. Its lacking a ton of features and many of the features it does have are poorly implimented.

      Try applying the same filter in GIMP and Photoshop, GIMP often looks like complete garbage. Some times it's fine but usualy its juts just a waste of time.

    4. Re:Gimp Isnt enough. by Lehk228 · · Score: 3, Funny

      actually i think he may be ON his period.... don't mess with him.

      --
      Snowden and Manning are heroes.
    5. Re:Gimp Isnt enough. by JourneyExpertApe · · Score: 1

      Since when were photoshopers "professionals"?

      --
      If you can read this sig, you're too close.
    6. Re:Gimp Isnt enough. by Anonymous Coward · · Score: 0

      So why post if you have nothing to add?

    7. Re:Gimp Isnt enough. by j79 · · Score: 1

      Period?

      Nah, I'm sure he was just referring to the Pantone Matching System...

    8. Re:Gimp Isnt enough. by tftp · · Score: 1

      Open your mailbox and have a look at 100+ flyers from the neighborhood's stores. The flyers are all images. Each image is made by a professional - at least because the creator of the image was paid for his work. There is a huge market for image making and processing.

  5. I don't agree... by Anonymous Coward · · Score: 2, Interesting

    I think there is demand for many other programs for linux that have no real FOSS alternative....
    Autocad, Exchange, etc... the difference here is that the people who need it don't generally go whining and losing their time on surveys... they are serious workers who have a tool that has no subtitute and get on with the work and off with the whining.

    1. Re:I don't agree... by dbIII · · Score: 0, Offtopic
      I think there is demand for many other programs for linux that have no real FOSS alternative....
      Autocad
      CAD was the application for the *nix workstation. AutoCAD was the cheap cut down version that runs on PCs on MSDOS and later - do you really think McDonald Douglass use AutoCAD to do design drawings of aircraft? You can use commercial software on linux too.

      Exchange
      After administrating an Exchange box along with a pile of other things at one point I know that I should not take you seriously. There are several mail server programs on a wide range of platforms that are much better in many ways - you can't even do a mailbox backup on Exchange without shutting down the pile of services and I'm very happy that the only disaster recovery I did for it was as an exercise to check the procedure (nasty, finicky piece of software that it is).
    2. Re:I don't agree... by tftp · · Score: 1

      Besides, those software tools often cost so much (from 1 to 40 thousand dollars) that saving on the OS is ridiculous. Often an entire computer is bought and reserved for this one application, especially if it needs an expensive video card (AutoCAD), fast CPU (Microwave Office or CST or Ansoft) or when the software license is tied to the hardware.

    3. Re:I don't agree... by Pig+Hogger · · Score: 1
      do you really think McDonald Douglass use AutoCAD to do design drawings of aircraft?
      Of course not, they use "Aircraftcad"...
  6. Photoshop by Anonymous Coward · · Score: 5, Informative
    The article says:
    "It's also not really thought of as a "Windows" application in many shops. For many graphic pros, it's a Mac OS program."

    Then...
    "I was also told that while GIMP's functionality may rival Photoshop's, how you get there is very different. For instance, to users who know Photoshop, GIMP's SDI (Single Document Interface) can be confusing. In GIMP, each image gets a separate window, whereas Photoshop's MDI (Multiple Document Interface) groups them all together in a single window."
    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...
    1. Re:Photoshop by Anonymous Coward · · Score: 0

      Well in CS2 on Windows, Photoshop has essentially become a multiple document appplication, since although there is a desktop, windows aren't restricted to it. (I just wish they would bring Illustrator along with it) After Effects and Premiere are taking similar routes with their latest version, except with a primarily dock-based design (which resembles Visual Studio, oddly enough). They may have to work on the interface some more but it's a nice improvement.

    2. Re:Photoshop by olliej_nz · · Score: 3, Informative

      The big problem with colour management is that professional designs need access to Pantone colours -- and those have to be licensed

      --
      To be or not to be.-Shakespeare
      To do is to be.-Nietzsche
      To be is to do.-Sartre
      Do be do be do.-Sinatra
    3. Re:Photoshop by Jeff+DeMaagd · · Score: 1

      Is there really a licence issue for closed plug-ins? That doesn't seem to make sense unless the plug-in itself uses GPL'ed code. If there is something about the plug-in interface that requires GPL code, then I understand in a way, but I would expect that interface to be easily documented or reverse engineered.

      IIRC, there are patents covering some of the color management, so while it is solvable with code, that code wouldn't be legally distributable in any countries that use that system.

    4. Re:Photoshop by Anonymous Coward · · Score: 4, Interesting

      You just demonstrated that you don't understand the "big problem" with color management. Formal color management is about reconciling various RGB and CMYK color spaces in a perceptually consistent way (i.e., transforming monitor color to printer color), and has nearly nothing to do with licensing. Spot colors like PANTONE are a very small subset of the domain of color management.

    5. Re:Photoshop by Anonymous Coward · · Score: 0

      Hi. I'm a typical slashdot reader. I spend all my time downloading music off the internet (information wants to be free!) I don't understand the problem.

    6. Re:Photoshop by Farmer+Tim · · Score: 3, Insightful

      Spot colors like PANTONE are a very small subset of the domain of color management.

      While spot colours may be a small part of the technical side of colour management, the ability to shave several hundred dollars off the cost of a print run by using a two or three tone Pantone process rather than full CMYK is far from trivial if you want to stay in the print business. And that's before you even think about special finishes (like metallic), which can't be specified in CMYK or RGB at all.

      --
      Blank until /. makes another boneheaded UI decision.
    7. Re:Photoshop by Ambush · · Score: 1
      Not to mention all the licensing fun of releasing closed plugins for a GPL application. That'd be fun...

      You mean like video drivers (http://www.nvidia.com/object/unix.html) for Linux maybe?

      --
      There are 10 kinds of people; those who know ternary, those who don't, and those now hunting for a dictionary.
    8. Re:Photoshop by McDutchie · · Score: 1
      Photoshop is a SDI application on the Mac.

      No, it isn't. All (native) Mac applications are MDI; it is fundamental to the Mac's user interface. The difference is that the Mac does MDI right by not embedding document windows in a big application window; the screen is the (transparent) application window, with the menu bar at the top, where it belongs. But it is still MDI because the same instance of an application opens several documents, not just one.

    9. Re:Photoshop by Hosiah · · Score: 1
      third-parties won't write GIMP plugins until companies start using it,

      Could somebody, anybody, anybody at all, explain how this absolutely insane misconception got started? Gimp has plug-ins. It has always had plug-ins. You can write more of your own plug-ins using the Scheme-like script-fu language. SEE?

    10. Re:Photoshop by Hosiah · · Score: 1
      You just demonstrated that you don't understand the "big problem" with color management.

      Like with any of these plug-ins? By the way, perhaps next time we should be careful taking the word about FOSS from a site with Microsoft ads all over it.

    11. Re:Photoshop by damppa · · Score: 1

      Photoshop is a SDI application on the Mac. SDI vs MDI is hardly the reason professionals will not switch to The GIMP.
       
      Yes, but Mac OS is designed to work as SDI, whereas Gnome, KDE and Windows are not - and that's why gimp sucks donkeyballs on these platforms. It's *very* easy to get lost with Gimp app windows in all of them - whereas in Mac selecting Photoshop from Dock selects all photoshop windows as they were one single MDI app.

  7. Preview mode on Unsharp Mask by interiot · · Score: 1

    That's the biggest one for me. Though I'm consistently learning new things about Photoshop despite learning quite a bit about it, and am consistently running into roadblocks with GIMP. As far as I can tell , GIMP isn't actively catching up, it's still got a long ways to go.

    1. Re:Preview mode on Unsharp Mask by zerblat · · Score: 1

      What version are you using? GIMP has had a preview for unsharp mask since at least version 2.2.

      --
      Please alter my pants as fashion dictates.
  8. Photography Studio by Anonymous Coward · · Score: 0

    I work for a photography studio and considered switching to Linux and GIMP to save some $6,000 /year on software bills, but it is definately lacking essencials,

    1. Re:Photography Studio by Anonymous Coward · · Score: 0

      but it is definately lacking essencials,

      Like spellcheck?

  9. GIMP won't natively process in 16bpp images by gorim · · Score: 4, Informative

    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.

    1. Re:GIMP won't natively process in 16bpp images by zippthorne · · Score: 1

      While I agree that GIMP should support greater depth of colors, and possibly even abstract the colordepth to the point that it's arbitrary (and thus infinitly expandible), you must realize that GIMP is probably never going to be able to support your RAW photos, for the simple fact that RAW isn't a consistant format.
      Some companies aren't even consistant across all their camera lines. And of course, the formats or algorithms are in varying states of copyright, patent, or trade secret.

      --
      Can you be Even More Awesome?!
    2. Re:GIMP won't natively process in 16bpp images by Lobais · · Score: 2, Interesting

      8bpp? Doesn't gimp work with 24bpp? 256^3?

    3. Re:GIMP won't natively process in 16bpp images by tftp · · Score: 1
      Some companies aren't even consistant across all their camera lines. And of course, the formats or algorithms are in varying states of copyright, patent, or trade secret.

      It doesn't matter, as long as his camera comes with the software that does the job. If gorim needs RAW, for whatever goal, then GIMP is not an option for him. When people spend big bucks on good cameras they probably know what they are doing.

    4. Re:GIMP won't natively process in 16bpp images by Saeed+al-Sahaf · · Score: 1

      No.

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    5. Re:GIMP won't natively process in 16bpp images by RDW · · Score: 1

      'GIMP is probably never going to be able to support your RAW photos'

      There's already an excellent solution to this problem:

      http://www.cybercom.net/~dcoffin/dcraw/

      It's been used to create several GIMP plugins, including:

      http://ufraw.sourceforge.net/

      When run in 'standalone' mode, UFRaw even has a 16-bit output mode (useful if you Cinepaint). When run as a GIMP plugin, you're obviously stuck with GIMP's 8-bit limit.

    6. Re:GIMP won't natively process in 16bpp images by MarkoNo5 · · Score: 1

      He meant 16 bits per channel, which is 48 bits per pixel. GIMP can only use 8 bits per channel, resulting in 24 bits per pixel.

    7. Re:GIMP won't natively process in 16bpp images by Hosiah · · Score: 1
      RAW photos in 16-bit

      Have you tried this Gimp derivative? It has support up to 32-bit.

    8. Re:GIMP won't natively process in 16bpp images by rufty_tufty · · Score: 1

      As a home user who does spend big bucks on his camera, i don't have money left to spend on the manipulation software :-)

      That said I don't do the kind of manipulation that needs anything more than GIMP can offer (yet, but I'm getting close)

      --
      "The weirdest thing about a mind, is that every answer that you find, is the basis of a brand new cliche" -
    9. Re:GIMP won't natively process in 16bpp images by BenjyD · · Score: 1

      "Firefox can't find the server at cinepaint.movieeditor.com"

  10. UI by Anonymous Coward · · Score: 0

    The one thing that stopped me from even considering GIMP was the UI. I shouldn't have to spend more than 20 minutes learning a new interface. To those die-hard Linux fans out there - I know gimp doesn't claim to be a photoshop replacement, but sometimes I think that is just an excuse for its various shortcomings.

    1. Re:UI by Theatetus · · Score: 1
      I shouldn't have to spend more than 20 minutes learning a new interface

      If you are saying it took you less than 20 minutes to learn Photoshop, I'm going to laugh my ass off. Photoshop's UI is extremely confusing, just like GIMP's is. The only specific shortcoming I can ever nail people down on is that it's "not like photoshop". No, it's not. It does some stuff better and some stuff worse. On the whole I tend to be less surprised by GIMP's UI than photoshop's, but then I've been using UNIX variants for about 15 years now and probably have some of the same mental metaphors that the GIMP team did. If you're honestly claiming that graphic artists are forever tied down to the same UI because companies can't afford a few days of downtime while they learn a new one, I'm also going to laugh my ass off.

      --
      All's true that is mistrusted
    2. Re:UI by Anonymous Coward · · Score: 0

      I meant learning GIMP from Photoshop, and yes - taking a few days downtime for a company is a huge deal. A single graphics artists can cost several hundred dollars a day. Multiply that by a bunch of graphics artists and a few days and it dwarfs the cost of photoshop.

      And your thing about how gimp isn't photoshop - that is my main complaint of it. As the article says, photoshop can't be replaced by a single application because it is a platform. I applaud gimp's creators for making a very fine product, but i will continue to use photoshop for the forseeable future because gimp does not even come close to competing with it.

  11. Only the real thing by Anonymous Coward · · Score: 1, Insightful

    People want real AAA products instead of crappy knock offs? Amazing!

  12. The Standard by nife00 · · Score: 2, Informative

    Adobe photoshop is the standard. Every graphic artist learns on photoshop. Every little quirk or oddity of gimp makes life that much harder. No matter how great the image manipulation code is. The gimp interface is just not the standard and that loss of productivity means gimp is at a serious disatvantage.

    1. Re:The Standard by Homr+Zodyssey · · Score: 1

      I'll be one of the first to admit that GIMP has its weaknesses. However, you can't diss on a program just because it doesn't look/act just like the one you were trained on. This kind of mentality would prevent anyone from ever releasing new software.

    2. Re:The Standard by luvirini · · Score: 1

      That is the reason most good new programs use interfaces that are very close to the orginal ones.. and only making it better in small ways, so people get comfortable.

    3. Re:The Standard by LurkerXXX · · Score: 1

      You certainly can if someone is trying to convince you to switch as the author of the article wanted his Photoshop using friends to. If it doesn't look/act the same you lose time learning it. You lose time getting used to using it so that all those shortcuts are second nature to you. When you bill at around $100/hour, the time involved in learning the new system, finding and installing all those 'hack' workarounds to get it kinda/sorta simalar to what you are used to, and the time it slows you down until those new commands all become 2nd nature... That time adds up to more than the next several upgrade versions of 'Real' program are going to cost you! Plus all the lost functionality of the plugins, 16-bit color, etc, etc. Why switch??? If your doing it for a hobbie, sure. If your doing it for work it would be a really dumb move.

    4. Re:The Standard by BluBrick · · Score: 1
      Photoshop's interface is the standard. So what?

      Ed is the standard text editor!

      Standard != Best (as much as it should be, it just ain't necessarily so)

      --
      Ahh - My eye!
      The doctor said I'm not supposed to get Slashdot in it!
    5. Re:The Standard by mgabrys_sf · · Score: 1

      I love the geek mentality that represents a violation of the first rule of any product. Fill a need. By trying to be a photoshop killer without being photoshop like, most artists and designers have given it the cold shoulder.

      The response from the geek community? "the customer is wrong and needs to work the way we made it work".

      With customer support and feedback like that - is it any wonder open source is a joke? Dollars equals votes equals sales equals company staying in business keeping customers happy.

      Open source - we fuck around - we give it to you - insult you if you don't like it - and then mastrubate to Hentai porn.

      Back to work amigo!

  13. Krita by Andrew+Tanenbaum · · Score: 3, Informative

    It's not there yet, but look out for Krita. It has great ICCM colour support, but it's kind of slow.

    1. Re:Krita by nife00 · · Score: 2, Informative

      http://www.koffice.org/krita/
      It looks like its closer to the photoshop interface. Though it does look like it has fewer features right now.

    2. Re:Krita by Illissius · · Score: 3, Informative

      Krita 1.5 will have, among other things, object layers, group layers, adjustment layers, RGB8, RGB16, CMYK8, CMYK16, L*a*b*16, RGB float 16 and 32 (OpenEXR), LMS32, grayscale, and even a Watercolors colorspace. That's a whole lot of GIMP's deficiencies right off the bat. However, it also (a) is slow (most effort so far has gone into architecture and features, not optimizing), and (b) has an even smaller plugin community than the GIMP's, due to it being pretty new. (On the other hand, nearly everything in Krita is a plugin, including colorspaces, tools, paintops, and obviously filters, so once it picks up it could be pretty nice.)

      --
      Work is punishment for failing to procrastinate effectively.
    3. Re:Krita by cortana · · Score: 1

      Holy crap, that's fantastic. Maybe the added competition will light a fire under the Gimp developers' arses! It's just a shame Krita will almost certainly be hobbled by MDI... :)

    4. Re:Krita by Paul+Slocum · · Score: 1

      Looks pretty cool, too bad it's not available for Windows.

    5. Re:Krita by BlueLightning · · Score: 1

      After KDE moves to Qt 4 (which will be in KDE 4) this could change, if the right people take charge of porting and maintaining it.

  14. Irfanview by Bemmu · · Score: 3, Interesting

    GIMP is cool, a bit unixy but for a novice it accomplishes much the same as more expensive programs. The thing I'm most missing on my desktop is Irfanview. How to move hundreds of pics from digicam to the computer, crop and rename? GIMP is very unsuitable for this task. Heard it's possible to get Irfanview to run on WINE, though, but a native solution would always be nicer.

    1. Re:Irfanview by Anonymous Coward · · Score: 0

      gqview

    2. Re:Irfanview by dbIII · · Score: 1
      How to move hundreds of pics from digicam to the computer, crop and rename
      ImageMagik called from a script - why use a GUI for hours to do a repetitive task when you can kick off a script and come back in the morning?
    3. Re:Irfanview by vrt3 · · Score: 1

      Have you tried XnView? I don't use it, but from the description it looks as if can do more or less the same thing as IrfanView.

      --
      This sig under construction. Please check back later.
    4. Re:Irfanview by dodobh · · Score: 1

      ImageMagick + your friendly file manager?

      --
      I can throw myself at the ground, and miss.
    5. Re:Irfanview by tero · · Score: 1

      Several options...

      As already pointed out, ImageMagick and some scripting will keep you going forever..however if you're not into that there are some graphical tools:

      http://gthumb.sourceforge.net/
      http://f-spot.org/Main_Page

      Also, check out this page:
      http://en.wikipedia.org/wiki/Comparison_of_image_v iewers

    6. Re:Irfanview by xouumalperxe · · Score: 1

      That's DEFINITELY the sort of thing I'd personally do with image magick and bash. Right tool for the right job. But I'm more than slightly oriented towards programming, so I'm biased. It's for less automated, more visual tasks I do think that a visually oriented suite would be best.

    7. Re:Irfanview by labratuk · · Score: 1
      --
      Malike Bamiyi wanted my assistance.
    8. Re:Irfanview by gg3po · · Score: 1
      How to move hundreds of pics from digicam to the computer, crop and rename?

      ImageMagick

      --
      ---
  15. Reason why people want Photoshop... by Skal+Tura · · Score: 1, Insightful

    Is that it's easy to use. PERIOD.

    GIMP might come close to the level of features of Photoshop (note: close), but nowhere near the usability & speed of production.

    If you want PROs to use your software it needs to be FAST, EASY & POWERFULL.
    As it currently is, Photoshop is faster, easier & more powerfull. So what's there to wonder?
    It's not like news that Photoshop is more wanted than GIMP, duh..

    1. Re:Reason why people want Photoshop... by Anonymous Coward · · Score: 2, Informative

      Photoshop is most certainly NOT easy to use. No professional-grade application is. It may, once you're used to it, be fairly efficient, but it sure as hell is not easy.

    2. Re:Reason why people want Photoshop... by gg3po · · Score: 1
      Is that it's easy to use. PERIOD.

      You must not be talking about the same Photoshop I've used. All Adobe products are notorious for poor UI design -- especially hiding features. PS is no exception.

      --
      ---
    3. Re:Reason why people want Photoshop... by Skal+Tura · · Score: 1

      Pros find it easy, and that's all that matters

      and yes, some feats are hard to find, but NOWHERE NEAR the level of hardness of GIMP.
      This reminds me of a quote which went something like "Democracy is the worst form of goverment, except for all of those tried", meaning that democracy might SUCK but it's best so far.
      Exactly same goes for Photoshop

      remember the "good ol' days" when you hard to read like 1000 page manual for GIMP just to find that the button for straight line is ALT with was it pencil being selected?
      Atleast it's not that hard to find some BASIC feats in PS ;)

  16. GimpShop by Anonymous Coward · · Score: 0
  17. I've used both extensively... by brian0918 · · Score: 3, Interesting

    I can easily say that the newer versions of Photoshop dwarf the competition. I specifically focus on restoration and cleanup of old photographs, and this is where Photoshop excels. Photoshop's layout seems much more straightforward, and its utilities more accessible and versatile than those in GIMP.

    1. Re:I've used both extensively... by Khaed · · Score: 1

      I've used both the same amount, and even older versions dwarf GIMP. My home system is currently Slackware without a trace of Windows (because I'm both cheap and honest), so this is coming from a seriously crazy Linux fan*, but if I had any real need for graphical design? I'd need Photoshop.

      * Sorry to other Slackware users, but to dive in with SW requires a certain amount of crazy.

  18. In other news... by TeachingMachines · · Score: 0, Flamebait

    After version 4.0, Photoshop became way too much for non-professional users, prompting for additional "scratch disks" during the install and requiring gig after gig of memory to run (even then) slow as molasses. Gimp is a welcome relief to both casual and advanced graphic designers, with just the right amount of power to keep us happy. Gimp's feature set shouldn't be driven by psycho "power users" anyway. It's fine the way it is.

    --

    The Death Penalty: Killing people to show others that killing people is wrong.
    1. Re:In other news... by Stevyn · · Score: 1

      I can't agree with you there. Each new version of photoshop is easier to use even though it packs in more features. Photoshop is the standard. GIMP may have the same capabilities, but it's user interface is crap. What's worse is how many people have made this argument and the GIMP people seem to ignore it thinking their shit doesn't stink.

  19. No, Gimp is not enough by Anonymous Coward · · Score: 1, Interesting

    The Gimp doesn't support 16bpp (and CinePaint has a different focus now) and also it doesn't have cool features like the shortcut for the crop-and-resize feature (in one press of a button) that Photoshop has.

    Additionally, Gimp is extremely slow (try to read a 100 MB TIFF file and then do the same on Photoshop to see what I am talking about) and its UI is just pretty bad.

    Sure, non-professionals will be right at home with Gimp, but real PRO DSLR photographers need the above features, and much more.

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

    1. Re:Huh? by Anonymous Coward · · Score: 0

      Huh indeed. In case you didn't notice, Linux isn't just for serving webpages anymore.

    2. Re:Huh? by Otter · · Score: 2, Informative
      In case you didn't notice, Linux isn't just for serving webpages anymore.

      Note that the survey asks what apps are required for "switching to Linux in their data center", not what's needed before your mom will let you install it on the family computer.

    3. Re:Huh? by Nermal6693 · · Score: 1

      Which actually makes me wonder why iTunes and World of Warcraft are in the list.

    4. Re:Huh? by NoMoreNicksLeft · · Score: 1

      Stalled in the stoneage? It's amazing how if people have to look in a different menu for a feature, it doesn't exist.

      I wonder if that's what it takes, cloning photoshop down to the last pixel, just so you retards would give it a little respect. Of course, ravenous flesh-eating lawyers would descend upon the gimp developers...

      There are so many valid criticisms of Gimp (as there is with all free software), that I don't know why people have to come up with what amounts to pure bullshit. It boils down to what is fashionable for most, and short of them rubberstamping an "Adobe" logo on the thing no one will take it seriously.

    5. Re:Huh? by westlake · · Score: 1
      99% of business desktops don't have Photoshop

      But if a business is doing any photo editing in-house it will be using Photoshop. It's a small step from there to one-stop shopping at Adobe for all your desktop publishing needs.

    6. Re:Huh? by Nermal6693 · · Score: 1

      Aaaand, just to reply to my own pseudo-question, the previous survey question asks whether it's for your desktop or data centre.

    7. Re:Huh? by ciroknight · · Score: 1

      "In my opinion, rewriting GIMP from scratch and making it extensible would be the best choice."

      I've been saying this for years. Everything usable out of the GIMP can be salvaged (it's written in C so it's rather straight forward to save blocks of the code; no deep bound objects to extract). On top of that, it wouldn't take long to implement a new editor like Pixel, or better yet, pressure this guy into Open Sourcing his projet with a fat check written by some Linux-friendly organization (Redhat? Ubuntu? Novell?).

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    8. Re:Huh? by prockcore · · Score: 1

      The GIMP, as good as it is^H^Hwas, has stalled in the stoneage, while Photoshop has evolved.

      That's not true, the Gimp is moving along.. maybe not as fast as it should though.

      Photoshop is indeed a moving target. People talk about "needing 16-bit color channels", but photoshop itself only got them a few years ago.

      One thing the author touched on was that the de facto standard is often the standard du jour.

      Yesterday Quark dominated the newspaper industry, today it's Adobe inDesign. (Although inDesign still doesn't have a route-based workflow management).. something integrators have offered for quark for over a decade now. Tomorrow it could be Scribus.

      Yesterday all pre-press was done with PageMaker, today it's done with photoshop, tomorrow, who knows, it could be the gimp.

      You can't say which way the industry will tilt.. photoshop won't be king of the hill forever.

    9. Re:Huh? by finnif · · Score: 2, Informative

      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.

      You're aboslutely right -- except that 99% you're talking about also wouldn't be voting in this poll because they could get Photoshop if they need it. You're ignoring that a huge percentage of non-web-development professionals sit down in front of Linux boxes every day: they're working on movies and video games. You are aware that ILM, Dreamworks, Sony, WETA--just to name a few--have their artists working on Linux, right? That's a several thousand people who daily sit down and struggle without Photoshop. Gimp is a sorry substitute, and most shops have the Photoshop centric positions (art department, matte painters) still on Windows or Mac as a result.

      Before you go off saying I don't know what I'm talking about, I am a professional in that industry. Gimp was offered as a solution to me at a former employer on Linux, when Photoshop on SGI was dying off (yes, Photoshop ran on IRIX!). At the time, I said we better figure out a way to get WINE to run Photoshop, because Gimp does not cut it for mortals. Gimp still does not cut it nearly 8 years later. I'll take my current shop where we work on Windows and I have a COM-scriptable Photoshop CS2, thank you very much.

    10. Re:Huh? by killjoe · · Score: 1

      Photoshop in the datacenter? Clearly this survey is messed up. Chances are 15 year olds just spammed the survey and put down what they wished for the most which is a free photoshop. I guess a free GIMP isn't good enough for them and they are tired of stealing photoshop.

      --
      evil is as evil does
    11. Re:Huh? by Anonymous Coward · · Score: 0

      depth (16-bit)

      The Gimp supported 16 bit color channels before Photoshop did.

    12. Re:Huh? by wclacy · · Score: 1

      Most Data Center apps that run only on Windows have better linux alternatives. Or at least that is one way of reading the survey.
      You might also note that the top 10 list changed after the results were first published. The initial results were mainly from Novell Customers, and subscribers of Novell's Newsletters.

    13. Re:Huh? by Anonymous Coward · · Score: 0
      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.

      It's even worse than that. 99% of home users don't have Photoshop... unless they've pirated the damn thing. It's an expensive application and very few people actually need (or can even use) the features it offers.

    14. Re:Huh? by miyako · · Score: 1

      Actually, Linux has a pretty strong following for 3D modeling. A lot of studios use Maya on Linux for 3D modeling/rendering. I do a lot of 3D modeling, and I use Linux for almost everything. Among the other 3D artists I know, about half use Linux, and the other half is divided around 70%/30% between mac and windows. Many people bound to Mac or Windows are on those systems because of Photoshop.

      --
      Famous Last Words: "hmm...wikipedia says it's edible"
    15. Re:Huh? by typical · · Score: 1

      In my opinion, rewriting GIMP from scratch and making it extensible would be the best choice.

      You mean like instead of making your primitive a bunch of stored images and a set of operations that can be applied to them, making your primitives images and DAG operations (thus allowing going back in a history of image editing and modifying a parameter or so)?

      Good thing the GIMP people feel the same way.

      --
      Any program relying on (nontrivial) preemptive multithreading will be buggy.
    16. Re:Huh? by Rakishi · · Score: 1

      Huh? Why would it be free? Jus because it runs on linux doesn't mean you don't have to pay for it. Also, the survey lists Desktop in one of the questions so I assume it means "what do you need to move your business to Linux." I guess you can reconcile that with the rest of the question by assuming that they run windows in their data center since they need to run windows on their desktops. Personally I think someone failed to write the survey question correctly.

    17. Re:Huh? by killjoe · · Score: 1

      "Also, the survey lists Desktop in one of the questions so I assume it means "what do you need to move your business to Linux.""

      What percentage of businesses do their own graphic work? I would say less then 5%. Even in a windows shop that does their own graphics processing the graphics shop runs macs anyway.

      This survey cleary messed up.

      --
      evil is as evil does
    18. Re:Huh? by Rakishi · · Score: 1

      [sarcasm]And you can't move to Linux from a Mac why exactly? Is there some voodoo that Apple casts on owners which keeps them from ever switching to something else? Well thank you for telling me, I'll be sure to never ever buy an Apple product as the last thing I want is them messing with my mind. [/sarcasm]

      It seems you are missing the point of the survey or simply had not read it. Had you read the survey you would have realized why it exists and thus why your point is so utterly stupid. The point is to convince the makers of certain products to create linux versions so that companies who want to can switch to linux.

      It doesn't matter if it's 5% or 50%, if the rest has no critical apps, a lot of them or don't ever plan to switch then the survey is not for them. The survey is for those who are considering linux already (hey, there goes 90% of the market) but a few apps are holding them back. As was mentioned already, many graphics shops already use linux however for certain work the lack of Photoshop is holding them back.

      Also, reading it again the data center point it seems is an example and not really part of the question.

    19. Re:Huh? by bm_luethke · · Score: 1

      Maybe, maybe not. It could mean quite a few different things.

      It could also mean that the rest of the Linux world is pretty decent - I see no reason to ask for a word processing suite, DHCP servers, printer control, compilers, or many other sorts of products. In quite a number of those cases I prefer the Linux tool above the windows one anyway.

      This didn't really ask why you were not using Linux or what it needs to do for you to use, it asked what windows only (though they fail this in that several of thier choices are on a Mac also - they really mean "not ported to Linux) might keep you from it.

      For most there isn't going to be a single hard reason. It's like a lot of other things - I can name individual ideas that certain politicians have that I don't like, yet there aren't any real single issues that make or break me. Though if asked I could probably name my number one issue - but simply fixing it will most likely not change too much.

      What this most likely tells me is that Photoshop is one of those applications that many people use (and I bet mostly pirated) and don't really want to part with. If all thier other problems were fixed then they may change. Of course for any business that photoshop is a hard requirement it most likely isn't going to switch over either.

      Heck I use Linux quite a bit, am a software engineer, and one of my main gripes is not having photoshop (for the reason I initially stated - the Opensource option is either 98% as good or better in all the other apps I use. You will note I use openoffice even though I can easily get a liscense for Office). The other is lack of games, since my main home computer is gaming/image-video processing I use windows, the rest of my machines are Linux. If you had a good image processor and Wine played my games decently (or they had Linux clients) I wouldn't look back.

      --
      ------- Sorry about the spelling, I suffer from two problems. Dyslexia makes it difficult to spell well, lazy makes it
    20. Re:Huh? by killjoe · · Score: 1

      "The point is to convince the makers of certain products to create linux versions so that companies who want to can switch to linux."

      IT will never happen.

      "It doesn't matter if it's 5% or 50%, if the rest has no critical apps, a lot of them or don't ever plan to switch then the survey is not for them"

      YEs it does matter. If you have money and energy to spend then it's better to spend your resources going after 95% of the market rather then 5% of the market.

      Novell needs to spend it's time making openexchange, outlook plug ins, evolution better. Every single company in the world uses email. Why spend even a day thinking about winning over Mac shops? It will never happen.

      --
      evil is as evil does
    21. Re:Huh? by moranar · · Score: 1

      In my opinion, rewriting GIMP from scratch and making it extensible would be the best choice.

      Yes, because it did a whole lot of good to Mozilla. They sure were N1 after the code was written back from scratch.
      And btw, can't you write and install python plugins in GIMP? Do those need to be compiled too?

      --
      "I think it would be a good idea!"
      Gandhi, about Internet Security
    22. Re:Huh? by AigariusDebian · · Score: 1
      Stalled in the stoneage? It's amazing how if people have to look in a different menu for a feature, it doesn't exist.


      * support for high bit colors, so that one can open RAW files directly and edit them at full power.
      * all filters as layers, so that you can put a 20-30 layers on the picture, see the result and then go back to the third filter you put on it and tweak some setting of that filter there
      * smart sharpening and noise removal with profilization for a specific digital camera, scanner or film type
      * multifile save - have a primary document in xcf format and several secondary documents with, for example, three different jpegs with different sive and compression levels, so that when you press save for the primary document, the secondaries are automatically updated
      * batch processing mode including RAW support

      Some of this is in Photoshop, some of it is in Photoshop supporting tools. GIMP is a bit stale in comparison.

      (Note: I am a very enthusiastic FLOSS advocate, but I do not go against the facts.)
    23. Re:Huh? by NoMoreNicksLeft · · Score: 1

      * support for high bit colors, so that one can open RAW files directly and edit them at full power.

      It needs this for CYMK as much as for RAW.

      * multifile save - have a primary document in xcf format and several secondary documents with, for example, three different jpegs with different sive and compression levels, so that when you press save for the primary document, the secondaries are automatically updated

      No idea why anyone would want this, but it's a trivial feature.

      * batch processing mode including RAW support

      Wrong tool, in all likelyhood. Maybe some integration/cooperation with ImageMagicke though?

    24. Re:Huh? by cerberusss · · Score: 1
      At the time, I said we better figure out a way to get WINE to run Photoshop

      For $40, you can buy the commercial version of Wine called CrossOver Office. They heavily sponsor and commit to Wine sources. Photoshop has several entries in the compatibility database. Version 7 has a "silver medal", however CS and CS2 are known not to work.

      --
      8 of 13 people found this answer helpful. Did you?
    25. Re:Huh? by Anonymous Coward · · Score: 0
      Wrong tool, in all likelyhood. Maybe some integration/cooperation with ImageMagicke though?
      Exactly. I don't think photoshop fits in very well with unix philosophy of small, specialized programs being the huge, bloated piece of ass that it is. I don't think the Gimp should be trying to copy photoshop but rather to carve out its own niche, which it has been doing rather well.
    26. Re:Huh? by Hosiah · · Score: 1
      Before you go off saying I don't know what I'm talking about, I am a professional in that industry.

      OK, I'll bite. What is so terrible about Gimp? What can't you do in Gimp? I've been writing about Gimp and making tutorials about Gimp at my blog (see signature) for a while, and inviting people to ask questions about it. Your input could help. Not flamage, mind you. Input.

    27. Re:Huh? by SComps · · Score: 1


      I wonder if that's what it takes, cloning photoshop down to the last pixel, just so you retards would give it a little respect. Of course, ravenous flesh-eating lawyers would descend upon the gimp developers...



      Attitudes like that don't help either. Being called a "retard" by somebody that is trying to induce me to use a product isn't the best possible method. Then again, that's typical of geekdom. If somebody doesn't know exactly what you know, exactly the way you learned it and absolutely agree with every thought process you have; they are obviously inferior and therefore must be eliminated.

      Good job!

    28. Re:Huh? by ThePhilips · · Score: 1

      WHAT?????

      Have *ever* tried to use/compile ImageMagik? - I did it twice with two different versions. It took about 6-8 hours and failed in the end with obscure messages. Before putting something into comaprision you have to have first hand experience with it. (Proper alternative would be "netpbm". Check it out.)

      Unix phylosopy, as much I love it, does apply here quite differently. Photoshop is really a platform. Photoshop *is* Unix. Photoshop is a platform for small easy-to-develop application (a.k.a. plug-ins). As there are much small applications for Unix, there is plenty of plug-ins for Photoshop.

      In the end, I'm confused equally with both. Thou on couple of occasions had better luck with Photoshop. On Linux I use normaly netpbm - fits me right.

      --
      All hope abandon ye who enter here.
    29. Re:Huh? by jvp · · Score: 1

      Wrong tool, in all likelyhood.

      But Photoshop IS the right tool for this. Here's an example: You've come back from shooting 500-some RAW images. Fortunately, they were all done in the same setting, with the same lighting. One of the things RAW images need is White Balance processing. Since you shot all of these images in the same setting, the White Balance will be the same for them all.

      In PS: Open one of the RAW images, set the White Balance accordingly, and save the settings. On each of the rest of them, you script:
      - open file
      - apply white balance
      - balance color
      - scale (maybe?)
      - set an Unsharp Mask (maybe?)
      - save as TIFF

      This all works under PS wonderfully because, with the first image, you can SEE what your changes are doing.

      jas

      --
      Jason Van Patten
    30. Re:Huh? by Kadin2048 · · Score: 1

      Wow, I was totally unaware of that program.

      Here's a link to his actual page (with screenshots):
      http://www.kanzelsberger.com/pixel/?page_id=5

      It looks fairly impressive. The interface is honestly a clone of Photoshop, which is a huge plus in my book (nothing to relearn), it supposedly has CMYK support, works with TWAIN and SANE scanners, even does JPEG-2000.

      Not bad for $32! The license lets you run it on multiple platforms also, and he's got versions for MacOS, MorphOS, Linux (x86 and PPC), BSD (x86), and a list of others.

      I'll have to look into it more, but I might be cutting this guy a check soon, if it's for real and as good as advertised. I don't mind terribly the fact that it's not open-sourced, that's his choice as the developer, although it'd be nice to have some sort of promise that if he decides to stop developing it that he'll release it so it doesn't become abandonware. I suspect though in order to implement a lot of those features that there's a lot of licensed/patented code inside.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    31. Re:Huh? by NoMoreNicksLeft · · Score: 1

      Oh, don't get me wrong. I love helping out people who really want to learn to be computer users. I'll do my best. I was actually wondering how to best go about writing a patch for a gimp feature someone asked for in this thread. Something minor like that *might* be something I can handle.

      But don't get me wrong on the other end of the things, either. I have no interest in you using gimp, or linux, or anything else. Free software has proven that it doesn't need to appease mouth-breathing imbeciles. We finally get a chance to do software right, not software the way that will sell.

      So, as someone who just had to bite, prove yourself: what feature is gimp missing that photoshop has? Complaining that it's hard to get is fine, as long as you realize that is a minor thing (we all bitch about gimp's interface). But to say that it's a dealbreaker, that's just dumb.

    32. Re:Huh? by NoMoreNicksLeft · · Score: 1

      Do you have any idea what ImageMagick is? Do you understand how ignorant you sound?

      Mind you, I do consider that maybe it needs to be cooperative with Gimp, maybe some sort of plugin, so they talk to each other. But this just shows how sad it all is... the type of people bitching simply do not know what tools are used for what. What, are you going to complain next that gimp can't do batch scripts to rename files? (hint: bash)

    33. Re:Huh? by NoMoreNicksLeft · · Score: 1

      I think we can all agree that photoshop is unix, in the sense that it has 20 million different inconsistent graphical interfaces that all look like they're straight out of 1985.

      Past that, I don't know what you're talking about.

    34. Re:Huh? by SComps · · Score: 1

      Free software has proven that it doesn't need to appease mouth-breathing imbeciles. We finally get a chance to do software right, not software the way that will sell.

      Not to be complete sarcastic, but at least a little bit. Is that proof offered by the market share of Free software? Some of it rocks the planet. Postfix? amavis-new? Samba? even the linux kernel itself. The list goes on; including GIMP. These are fantastic applications and platforms; they fill their niche very well. Postfix, amavis-new? That's some power there man! I love it; but it sure was a bear to get set up properly. Hell I'm still not sure my implementation is set up properly but it works. Bigtime learning curve there. That puts off a lot of folks that might not be as bullheaded as I. Samba works really well, but the smbmount CLI has a lot of options for the uninitiated to think about. I'm sure you can see where this is going. Surprise I use them all; but like I said before. Somebody not as bullheaded as I might not spend the time dealing with that "Wha? it's not working!" situation. Hell, if it weren't for yet another fantastic application; Webmin, I'd have given up on CUPS a long time ago.

      So, as someone who just had to bite, prove yourself: what feature is gimp missing that photoshop has? Complaining that it's hard to get is fine, as long as you realize that is a minor thing (we all bitch about gimp's interface). But to say that it's a dealbreaker, that's just dumb

      First of all, I was speaking largely as a devils advocate. I use both Linux and Windows. When I'm using windows, I use Photoshop, when I'm using Linux, I use GIMP. While I admit I tend to get more frustrated trying to do things with GIMP; that's mostly because I spend more time in Photoshop. I'm definitely to be considered a novice at both however; so I'm probably not the best candidate for an actual evaluation of what it's missing. Several other people have brought up some very good issues however.

      Software the way it "should be written" needs to be functional, intuitive, easy to use and easy to learn. That doesn't mean it has to be crippled and non-technical; but the technical parts can certainly be exposed in intuitive places, with no-kidding workable defaults and possibly an "Advanced" button that delves into the levels that most novice users aren't going to want to mess with. Software can (and should) be powerful without being daunting. We're talking Photoshop or GIMP here; not scientific processing that requires a doctorate in genetic engineering.

    35. Re:Huh? by NoMoreNicksLeft · · Score: 1

      Anyone that says "uh, it's not working" only needs to ask me for me to do my best to help them. Sure, I get a little snippy, when they don't describe the problem very well the first try, but most days I'm in a decent enough mood to bite my tongue and help them figure out how to ask the question.

      Me, I tried qmail for my first. God, anything must be better. Postfix if I ever have occassion to set up another mailserver.

    36. Re:Huh? by jvp · · Score: 1

      Do you have any idea what ImageMagick is? Do you understand how ignorant you sound?

      I know precisely what ImageMagick is, and have played around with it for more than 10 years. Can you say the same?

      ImageMagick is no substitute for Photoshop's WYSIWYG RAW conversion processes.

      jas

      --
      Jason Van Patten
    37. Re:Huh? by NoMoreNicksLeft · · Score: 1

      Then you should have said "It's not powerful enough". That means, people need to add some features to it. It's the right tool, even if it's not refined enough yet. Instead, you'd have us bolt on functionality to gimp that probably doesn't belong there?

    38. Re:Huh? by finnif · · Score: 1

      OK, I'll bite. What is so terrible about Gimp? What can't you do in Gimp? I've been writing about Gimp and making tutorials about Gimp at my blog (see signature) for a while, and inviting people to ask questions about it. Your input could help. Not flamage, mind you. Input.

      I'm happy to oblige this, actually. I'll start at the beginning: installation on Windows. It's been a couple years since I tried using GIMP, so I wanted to install it to refresh my memory. I just downloaded the MSI installer and it won't let me install. It says I need to install the "GTK+ Runtime Environment" to use the GIMP. Now why they don't just include another piece of GPLed software in an MSI installer for Windows, where you can assume no one has GTK+ installed, I'll never know. Someone should fix this step and I'll be happy to try again, I've got too much work to do to mess around digging up other software to try this out again.

      A few things from memory are: alpha channel handling is poor and confusing, the right click context menu madness, and scripting in Scheme. The new versions of Photoshop have COM scripting on Windows, which means I can script it in whatever language I choose without writing hooks.

    39. Re:Huh? by Hosiah · · Score: 1
      GTK

      Hmmmm, OK, it's hard to install on Windows. In the first place, you're installing a piece of cross-platform software (try installing a Windows program on Linux and running it with WINE sometime. Fun!). In the second place, I can remember plenty of programs on Windows that needed special versions of ActiveX or dll's that I had to go chase down. I have no idea why this is a specific problem that just Gimp has. I would definitely advise using live CD's (I can only think of about five Linux distros that *don't* include Gimp. Even FreeSBIE, a BSD distro, has Gimp.): no install problems that way, and you can save your work to writable media. But granted, the Gimp team should get their installer to do it in one whack... they're probably thinking too much of Linux package management, where it all gets installed from one command, regardless of what you have and what it depends on. Once again, Gimp is blamed for problems that it turns out are just as much the fault of the non-native host system.

      Just about the rest of your refutations fall mostly apart. Alpha channel handling doesn't confuse me, regardless of whether it's in Gimp, Cinepaint, Image Magick, or SDL programming. It's termed "transparency" in the menus. You want to click with the left-mouse button instead of the right, is that it? Or you want that Gimp derivative somebody's writing that does the menus the exact way PS is laid out? (I forget what it's called, and I'm sick of Googling today. It was covered on Slashdot a while back.) And Windows COM scripting...you DO know that FOSS has programming languages Windows never even can dream of hosting, right? Meanwhile, if the FOSS world tries to make a move for DOM, either it will get patented (or is it already?), or GNU will get sued for another look-n-feel number, or they'll just add a new beanie feature and PS will be one feature ahead of Gimp again and then Gimp-vs-PS will rage on for another version because Gimp doesn't have beanies.

      Don't tell me you want to get me started on the features missing in Windows and Adobe that GNU, Linux, BSD, Solaris, and even plan9 from Bell Labs have. I haven't that long to live! But thank you anyway. This tells me something: the problems with Gimp that everybody complains about are actually problems with the *Windows* port of Gimp. Here's a good catch-all: Try Mediainlinux, see if you can get that downloaded and burned and running. It includes more image-editing tools than even *I* can remember, it runs live so you have nothing to worry about on installing, and it will expose you to more than *one* FOSS program, so you can get a better idea of this Unix-based thing, which, by the way, was thriving for years before Bill Gates ever *touched* a computer. Consider that pictures like this, this, and this were done from scratch using only the same tools you get on Mediainlinux. Surely, *somebody* can get use out of these tools, eh?

    40. Re:Huh? by finnif · · Score: 1

      Just about the rest of your refutations fall mostly apart.

      You guys wanted my input, but instead your flame-bait response pretty much backs up exactly what's wrong with slashdot and the attitude of the FOSS crowd.

      Let's go back over the facts: I'm a longtime user Photoshop. I have the money for Photoshop. After all of these years of using Photoshop, I don't like GIMP or the way it handles certain things in the UI. I don't like the fact that the installer requires me to go out and install a piece of FOSS separately instead of just including the darn thing (NO commercial Windows software would require this, sorry to burst your bubble).

      The traditional, ignorant /.er response is therefore it must be my issue that I don't understand the software. The correct software engineer response would be, "Hey, those are good software requirements that actually might be improvable." I think the problem with FOSS is that it's a lot of unpaid work, therefore if someone doesn't actually like the result, the response is "Tough shit, it's free software, improve it yourself." Well, my time is worth a lot of money, I'd rather just put $600 of that towards Photoshop and never think about GIMP again. And that's exactly what any professional who's not stuck on Linux would do.

    41. Re:Huh? by Hosiah · · Score: 1
      Hey, hey, whoa, wait a minute. I'm not the software engineer. Never said I was. I just write about it.

      Sorry to burst YOUR bubble, but I DID run Windows for a number of years, and it DID TOO have commercial software titles sold for it (read "games"!) which required extra packages not bundled with the software in order to run. Don't tell people they haven't seen what they've seen with their own two eyes and they won't flame you. Have you installed every single software program made for Windows onto Windows? Then how do you know? Have you tried every menu option in Gimp to do what you want? Then how do you know it can't be done? Hey, I have a bright idea, why don't you insist that other countries don't exist and then scream at anybody who tries to show you a map?

      It won't help you get what you want, what you're doing in here, unless all you want is attention.

    42. Re:Huh? by ciroknight · · Score: 1

      Well it really is as good as it's touted to be, but it's very limited and pretty buggy thanks to the fact that he is the sole developer on the project. I wouldn't mind it being closed source either if he actually had the money and staff to make it better, both of which he will never be getting as a closed-source project thanks to the 2 ton gorilla that is Adobe.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    43. Re:Huh? by finnif · · Score: 1

      Hey, hey, whoa, wait a minute. I'm not the software engineer. Never said I was. I just write about it.

      Are you, or are you not, interested in improving Gimp? Based on the thrashing you've been doing in these threads, I'm guessing you are not. You faked like you wanted to get feedback in that first post, but it's obvious that you feel we must all be forced to like Gimp exactly as it is.

      I checked out your blog and noticed you comparing Photoshop and Gimp, so let me ask you a question: how much money have you ever been paid to do work in Gimp? And exactly how long have you been using Gimp? It looks like you've only been writing about it for 2 weeks.

      Even though you're in denial about this, the people like myself who post that Gimp needs to work more like Photoshop are basically stating the obvious. Free or not, Gimp is following in the footsteps of the world's most popular photo editing software... how can it not be compared? I've been using Photoshop professionally for 15 years. I own it. Why would I want to change to software offers nothing new except a crappier UI, even if it was a commercial application? No commercial company has been able to convince Photoshop users that their product is better, and a lot have tried since 1990.

      So you might want to revisit exactly why you keep posting these very strange and defensive comments... instead focusing on what actually might be worthwhile to improve about Gimp. If you're that big a fan, make it a better program so that Photoshop users might actually like it. It's a truly worthless waste of energy to come on here to bash longtime Photoshop users for sticking with what they've got. Use that time to make it better if you believe so much in FOSS.

  21. 16bit Support by lhk · · Score: 1

    I've been using Photoshop for editing my photos (shot in RAW) for a few years now, and the greatest obstacle the prevents conversion to Gimp is lack of 16bit support. While 8bit certainly has enough depth for the final output, either for printing or the web, it is woefully insufficient for anything other than the slightest color or contrast manipulations; do a little levels or curves and the shadows get posterized.

    Besides that, advanced noise reduction (comparable to Noise Ninja or NeatImage), and sharpening (I currently use PhotoKit Sharpener) would be nice. However, I can live without these, so the deal breaker is 16bit support.

    lhk

  22. The truth is... by Liam+Slider · · Score: 1

    It's not Linux users that want Photoshop for the most part. It's some Windows users who want it to ever even consider Linux, mainly because they don't know any better.

    1. Re:The truth is... by nomadic · · Score: 1

      What do you mean "they don't know any better"? The article lists out specific, concrete things that photoshop has that the GIMP doesn't. It sounds like the artists he quotes know what they're talking about.

    2. Re:The truth is... by Anonymous Coward · · Score: 0

      There are Windows users that do professional graphics that would _like_ to use Linux, if for no other reason than the whole "Free as in Speech" thing.

      Photoshop, however, beats down The Gimp badly. Think Mike Tyson vs. Urkel.

      And if you're going to use WINE under linux to run Photoshop... well, you may as well just use Windows and be done with it.

      ~ as spoken by a highly opinionated professional graphic artist.

    3. Re:The truth is... by xouumalperxe · · Score: 1

      Or maybe some of them mentioned that they DID try the gimp, and pointed out reasons why it wasn't up to par. So perhaps the blokes that do it professionally DO know better.

  23. Artists' OS Knowledge by Bonker · · Score: 1, Interesting

    I'll offer a different reason that the GIMP sucking for real art tasks (It does.)

    Many college-degree artists can barely install Photoshop for themselves under OSX or WinXP. Installing any given Linux distro and then Installing the GIMP may be beyond them in the MAJORITY of cases.

    Without belittling anyone, their field of expertise is in Art and the creative process, not computer administration. They're *not* going to install GIMP on their home PCs and figure it out they way they may have been able to do with Photoshop or even Corel Paint.

    Usability issues aside, until a Linux/GIMP install is easy enough for the average artist to complete in about the same time they'd do a OSX/Photoshop install, GIMP isn't going to gain any real acceptance or artist input.

    --
    The next Slashdot story will be ready soon, but subscribers can beat the rush and slashdot the links early!
    1. Re:Artists' OS Knowledge by Anonymous Coward · · Score: 1, Informative

      until a Linux/GIMP install is easy enough for the average artist to complete in about the same time they'd do a OSX/Photoshop install, GIMP isn't going to gain any real acceptance or artist input.

      Gimp is available for both OSX and XP, which are about as easy to install as Photoshop.

    2. Re:Artists' OS Knowledge by Bemmu · · Score: 1

      Step 1: Insert Knoppix CD and boot
      Step 2: ???
      Step 3: GIMP!

    3. Re:Artists' OS Knowledge by SoupIsGoodFood_42 · · Score: 4, Interesting
      I have a diploma in computer graphic design and in mulitmedia. In both classes, there were heaps of who were very computer literate.

      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.

    4. Re:Artists' OS Knowledge by paintbrush12 · · Score: 1

      watch oh you pick on i'm a VSFX artist . ' i run 2 linux boxes . SUSE 9.3 and novel laptop. I"m capable of useing my photoshop 7 on a port and installign it myself. but i would perfer the sability of it as a native app. gimp is ok for quick useage .but it dosn't have near the depth that photoshop does .(i own licenses to v 7 and CS2) as for as artists cant yadda yadda . thanks lump us all as dump. tell it to pixar , or sideFX, or digital domain sure.. now lets loook at this from MY view . sitting her in my bed room now we have all 3 majior OSes, ther is a happy littel iMAC running OSX, another happy iMAc i beleive currently booted inot umbuntu... we have a dual boot lappy , thats win XP pro, and i think the other partion is a very small install of gentoo . on typeing this on my novel lappy . choose this distro because , it's light and the lappy is old . now at school Savannah College of Art and Design. we run a LINUX back bone . with dual boot (PC)computers . CentOS, or winXP pro. i have the perferance ot use the CentOS when i can and 90% OF MY maya WORK is on that os. the other 10% is done in windows because i need photoshop now at home i just downloaded houdini 8, aprentice RPM, i will be installign that probly tomarrow . we are taught linux for VSFX. and quite frankly from what i've seen most software really isn't that hard to install. they come with step by step instrutions. hell even gentoo walks you through an install. ' unless you have 2 weeks and wish ot do linux from scratch it's not that bad.(joke at our lug is 3rd time is the charm...) but just wished to chime in not all Artist are idiots .

    5. Re:Artists' OS Knowledge by KanSer · · Score: 2, Interesting

      It's called Ubuntu 5.10. It comes with GIMP. I gave a disk to a brain damaged man and he did it himself, no phone calls.

      I'm not even lying.

      --
      • MOD PARENT UP by Anonymous Coward Wednesday April 20, @4:20
    6. Re:Artists' OS Knowledge by AME · · Score: 2, Insightful
      Gimp is available for both OSX...

      Gimp for OSX requires X11. The average Mac user will not understand why they have to install this esoteric thing from their original OS install disks just to try out a graphics program. Then they will not understand why the main menu of the program (which by their reckoning is the one at the top of the screen -- the X11 menu) has absolutely nothing to do with the application that they are running.

      The toolbox in a separate window thing, which I actually like on Linux, doesn't work on Mac because the first click on a window in OSX selects the window and does not activate any elements in that window. This means that selecting a new tool requires double-clicking in the toolbox window. Then using the tool requires double-clicking in the image window -- once to select the window and once to use the tool.

      The entire GIMP user interface is alien on OSX. The application feels completely out of place. And this coming from someone who uses (and likes) the UI that everyone hates on his multi-head, multi-workspace Linux machine at work. In that environment, I like the separate toolbox and the separate image windows and the context menu. It works for me in that environment. But on OSX (which I'm running at home -- and have GIMP installed on) it just doesn't work.

      --
      "I have a good idea why it's hard to verify programs. They're usually wrong." --Manuel Blum, FOCS 94
    7. Re:Artists' OS Knowledge by Infernal+Device · · Score: 1

      GIMP isn't going to gain any real acceptance or artist input

      And the likely answer is going to be: "Well, if you want it, why don't you write it?".

      --
      "My God...it's full of trolls!"
    8. Re:Artists' OS Knowledge by Anonymous Coward · · Score: 1, Informative

      The GIMP has LAB mode (Image ----> Mode ------> Decompose)
      The GIMP is actually a pretty good program. It might lack some options, but it's still pretty usable even in a professional environment. I think though it's because everyone is used to photoshop that it's hard to get away from it.

    9. Re:Artists' OS Knowledge by SoupIsGoodFood_42 · · Score: 1
      It is a pretty good program, don't get me wrong. But even though these other features Photoshop has may seem trivial, they are BIG time savers. Some of my website mock-ups have over 50 layers. I even find that only having one level of layers folders to be a pain, sometimes. And effects are important because it means I can easly change a colour, image, or some other element without having to re-edit other layers.

      I think it's another one of those cases where programmers just don't see what the users are fussing over. Photoshop got where it is because it listened to what the users wanted. In many OSS projects it seems as if whatever the developer thinks is best, is the best.

    10. Re:Artists' OS Knowledge by typidemon · · Score: 1

      I used to tutor multimedia/graphic design students in their later physical computing studios. It is true that many of them were very computer savvy, the vast majority of them didn't really know the inner workings of a system. In fact, we had a 51% collusion rate in introduction to programming (the year before I started) because those students refused to study.

    11. Re:Artists' OS Knowledge by Ford+Prefect · · Score: 1
      The toolbox in a separate window thing, which I actually like on Linux, doesn't work on Mac because the first click on a window in OSX selects the window and does not activate any elements in that window. This means that selecting a new tool requires double-clicking in the toolbox window. Then using the tool requires double-clicking in the image window -- once to select the window and once to use the tool.

      Perhaps not ideal for the hypothetical 'average Mac user' who will have a fit if asked to go anywhere near a command-line, but the click-to-raise toolbox thing is easily fixed; quit X11.app and at the terminal, enter the following:
      defaults write com.apple.x11 wm_click_through -bool true
      Start The GIMP again, and behold! Clicking on the toolbox now works properly. Annoying that this has to be done, but personally I'd blame Apple for silly defaults... ;-)
      --
      Tedious Bloggy Stuff - hooray?
    12. Re:Artists' OS Knowledge by Anonymous Coward · · Score: 0

      No, but some of them have a quite freakishly hellish combination of ADHD, bad grammar, and an overdose of speed in their breakfast cereal.

    13. Re:Artists' OS Knowledge by Hosiah · · Score: 1

      Looks like you, too, could stand to have some misconceptions cleared away about the Gimp. Scroll down for the Gimp Info center halfway down on the left. Is this the LAB stuff you're talking about?

    14. Re:Artists' OS Knowledge by Guido+von+Guido · · Score: 1

      The GIMP has LAB, but I haven't found a way to preview the image. So I have to work with the individual L, A and B channels. This is a start, but it's a pain in the [insert body part here] to make some changes to the image, recompose it to see their effect, and then try again (and again and again) when it isn't quite right. Let me add that I use LAB extensively.

      In Photoshop, on the other hand you can make changes to the individual channels while simultaneously seeing their effect on your image. It's simpler, quicker and more powerful. In my opinion Photoshop is still markedly better than the GIMP.

    15. Re:Artists' OS Knowledge by SoupIsGoodFood_42 · · Score: 1

      As someone has already pointed out, I was wrong about LAB. Although, I do wonder why they couldn't call it LAB, rather than Decompose.

    16. Re:Artists' OS Knowledge by Guido+von+Guido · · Score: 1

      This is better than Image->Decompose->LAB, but it still doesn't approach Photoshop's ease of use or flexibility. There's still no way to preview your changes. For instance, with Photoshop I can open up an image in LAB, press Ctrl-M to open up curves and make small or large changes and see the effect immediately. I can change them repeatedly and as needed quickly and easily.

      With this plug-in, however, I have to make my changes, click OK to apply them, and then see what they look like. If I have to tweak the image, it looks like I have to back out of the changes and repeat the process. On a typical image this would be a real headache.

      Also, I don't see any way to manipulate LAB curves (i.e., no equivalent to Tools->Color Tools->Curves).

    17. Re:Artists' OS Knowledge by Hosiah · · Score: 1
      It's always like this. People charge in going "Gimp can't draw straight lines! Gimp can't draw black-and-white pixels! Gimp can't count to two!" and we patiently point out the three simple menu steps they could have used to do it if only they'd thought to look there, and without missing a beat they go on: "Yeah, but it doesn't SMELL, FEEL, TASTE, LOOK, AND SOUND EXACTLY LIKE PHOTOSHOP!"

      but it still doesn't approach Photoshop's ease of use or flexibility.

      Yeah, yeah, yeah. Whatever. I suppose pointing out "Layers->Colors->Curves" isn't going to do any good, either, is it? I mean, what the hell is this? Are you people forced to use a computer with your hands cuffed behind your back or something? Right-click. That's what the right mouse button is for. Explore *every* submenu, in order. Open a test image and run *every* menu entry on it. You don't even need to open this free book or read any of my tutorials or read anybody else's tutorials. Everything's right there. If you don't like it, don't use it, but stop insisting that all the functions don't exist. It's dumb. You have just as much access to Google as anybody else, presuming you don't live in China. And then people wonder why we get frustrated.

      As I've said before, I'm *dying* to see Photoshop ported. So *Adobe* can deal with you people instead of we GNU/Linux users.

    18. Re:Artists' OS Knowledge by maxwell+demon · · Score: 1
      Annoying that this has to be done, but personally I'd blame Apple for silly defaults... ;-)

      Why can't the installer for GIMP/Mac do this (or, if it isn't installed with an installer program, GIMP itself at first startup, just like it creates all those directories etc.)?
      --
      The Tao of math: The numbers you can count are not the real numbers.
    19. Re:Artists' OS Knowledge by Ford+Prefect · · Score: 1

      Why can't the installer for GIMP/Mac do this (or, if it isn't installed with an installer program, GIMP itself at first startup, just like it creates all those directories etc.)?

      There's no installer (like 'proper' Mac applications, you just drag the program from the disk image into your Applications folder), and by the time The GIMP itself is running, X11.app is already up and running so will ignore any configuration changes (probably just until it's next run, though).

      However, there is the 'Gimp.app' wrapper program which starts up X11, provides an icon for drag-and-drop, etc. - it would probably be fairly straightforward to add a 'Do you want this config option changing?' thing for when it's first run.

      I think I'll go and suggest that right now, actually. :-)

      --
      Tedious Bloggy Stuff - hooray?
    20. Re:Artists' OS Knowledge by Guido+von+Guido · · Score: 1

      There is no preview for the overall image if you use LAB curves under Gimp. You have to run curves individually on each channel, and then recombine the channels to see what they would look like. For many images I make large numbers of changes to the LAB curves. This is an incredible pain in the ass.

      In Photoshop, however, I convert the image to LAB. I open curves. I can see the results of each change as I make them.

      Got that? Curves work great in GIMP for RGB. Curves don't work great in GIMP for LAB. If curves worked the same for RGB and LAB in GIMP, I'd be happy.

      BTW, spare me the patronizing "you people" bullshit. I've been using Linux on the desktop at work since 1998. I use Windows for Photoshop and the occasional game.

    21. Re:Artists' OS Knowledge by Hosiah · · Score: 1
      I've been using Linux on the desktop at work since 1998.

      Jesus. I'm impressed. I'm awe-stricken. I'm perplexed why you don't also see that making live previews of curves should be a simple thing to do in a script-fu. I'm flabbergasted that you haven't learned, in these mighty 8 years of steady Linux patronage, the rule that for every one person with a problem, there are three other people who've had the same problem and one of them has written a fix for it, and all you have to do is Google. I'm astounded that you would expect everything to run from one program - maybe it'd be better done from Cinepaint instead? In fact, I am so incredulous that I think you're lying, and have never run Linux a day in your life, else you wouldn't have this If-They-Hand-You-The-Moon-Whine-Louder-Because-You -Dont-Have-The-Stars attitude.

    22. Re:Artists' OS Knowledge by Guido+von+Guido · · Score: 1

      I think the gimp developers have done a great job, but the truth of the matter is that for my purposes I found that the gimp was a hammer and I needed a screwdriver. I've found that I spend less time getting better results with Photoshop than I did with the gimp. There are some solutions in sight, but I want something right now.

      By the way, you're too funny. I was trying to explain some of the reasons why I preferred Photoshop over the gimp, so suddenly I'm a lying whiner. Uh huh. Have you thought about cutting down on the caffeine?

    23. Re:Artists' OS Knowledge by Hosiah · · Score: 1
      I was trying to explain some of the reasons why I preferred Photoshop over the gimp,

      See, that's the gotcha. Prefer what you want, and $DIETY bless you. Use the right tool for the job, the one that works for you. Nothing wrong with that. But when you try to explain why to a person who's used it for years, and your reasons why are non-factual claims, you will of course not be believed and be criticized for spreading FUD, which serves the further error of discouraging other new users from learning new things themselves. Everybody gives up, because they've been told over and over again that it's impossible, and starts repeating the lies to the next generation without even knowing they're lies.

      What if I said I liked Linux better than Windows? OK, now what if I said I liked Linux better than Windows because Windows is just a text mode terminal without graphics capabilities - would this not be wrong?

      Look, what exactly in the hell DO YOU WANT? You wannna free Photoshop? So you're gonna scream down the effort to build a free Photoshop in public, pillowry it for not have the one bell to go with all it's whistles, spread FUD against it to discourage other people from trying it or learning it, and cuss out anybody who tries to help you. Does this help you get what you want? No, not unless what you want is attention. Have you tried EVERY OPTION IN THE MENU? Cuz it could be there, under a different name and a different form. But you'd never try that, because the way you're used to is inherently superior to everybody else's way, just because YOU found it FIRST. You could search for it, maybe you're not the only person on the planet with that particular problem, maybe a whole group of people wrote a new plugin for it, but you'd never do that because it would slaughter your ego to think that you weren't the Lone Persecuted Soul with Unique Problems That Nobody Could Solve. You could go to the Gimp development team and give them some input so they hear from as many like you as possible, and maybe one of them will either try to code it into the next release, or explain why it can't be so (rule of thumb: the only things the open source application can't do are patented), but to do so would be forcing yourself to admit that the Gimp developers weren't a pack of evil crackers but were actually rational human being like yourself. Can't have that!!!

      Well, keep flaming Slashdot. I'm SURE that'll help you so much to achieve your goal. Sorry I couldn't help.

  24. adobe releases by binarybum · · Score: 2, Insightful

    From TFA: "After all, Adobe didn't even release Version 6 (acrobat) for Linux."

                  That's about as dissapointing as M$ not porting BOB to Linux.

    --
    ôó
    1. Re:adobe releases by TubeSteak · · Score: 2, Funny
      That's about as dissapointing as M$ not porting BOB to Linux.
      I'm not going to make the big switch to Linux unless I can take Clippy with me.

      Or that really cute dog that shows up in the search window.
      --
      [Fuck Beta]
      o0t!
    2. Re:adobe releases by SoupIsGoodFood_42 · · Score: 1

      Acrobat or Acrobat Reader?

  25. It's insanely too bad Adobe ported 1st to SGI by Thagg · · Score: 4, Interesting

    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.
    1. Re:It's insanely too bad Adobe ported 1st to SGI by Anonymous Coward · · Score: 0

      Not only did Adobe port Photoshop to the SGI, they also ported to the Sun. As someone who has used (suffered through) Photoshop for UNIX, I can assure you that you're not missing anything by sticking with the GIMP.

      The UNIX ports are just the Mac version bundled with a Mac emulator. This is not unlike those companies which offer a "Linux version" of their software by repackaging their program with a Windows XP install and VMWare.

    2. Re:It's insanely too bad Adobe ported 1st to SGI by Telvin_3d · · Score: 2
      "I'm sure that they'd sell many more than a few hundred copies to the Linux market. Maybe even a thousand."


      See, right there is why it will never happen. I would be suprised if 1000 copies even recouped the cost in time and effort of Adobe porting over their creative suite. They have no incentive. Anyone who needs the tools that they offer has no issue using either OSX or Windows profesionaly, and the people who refuse to use anything but Linux as part of the open source movement are never going to use a comercial product like Adobe produces anyways.
    3. Re:It's insanely too bad Adobe ported 1st to SGI by Telvin_3d · · Score: 1

      On the other hand, that took place in 1992/93. What version would that have been, Photoshop 2.0? 3.0? Comparing that to a modern piece of software, even one like the GIMP which isn't quite up to industry standards, is like comparing OSX to Windows 3.1

    4. Re:It's insanely too bad Adobe ported 1st to SGI by ArbitraryConstant · · Score: 1

      But that brings up another point. In 1993, look at what SGI had compared to PCs and Macs. They had better, graphically-oriented hardware, and they had a proper OS instead of what sufficed on PCs and Macs at the time (NT notwithstanding). There was a justification, a reason why it was better, and there were graphically-oriented people on the platform, who were potential users (even if they turned out to not buy many copies).

      Linux, for the most part, runs on exactly the same hardware that Windows and MacOS do, so no advantage there. They are both now protected memory, preemptive multitasking OSes, and again no advantage (at least not big enough for most people). And Linux users tend not to be the sort that need advanced photo editing, so there's even less of a market.

      --
      I rarely criticize things I don't care about.
    5. Re:It's insanely too bad Adobe ported 1st to SGI by DrXym · · Score: 1
      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.

      My understanding is that Photoshop on the PC & Mac share virtually 100% of the application source because both sit on a cross-platform framework. Considering that Adobe already produce Acrobat products on Linux, I wonder how technically infeasible a port to would be. My guess is "not very" and even "I bet they have a port running in a lab already". So why isn't it out there? Even assuming some guy had built it internally, it would still cost $$$ to QA, bugfix, document and sell. Perhaps there simply isn't the market out there for it.

    6. Re:It's insanely too bad Adobe ported 1st to SGI by canavan · · Score: 3, Informative

      Adobe most certainly sold thousands of copies of Photoshop 3.0 for IRIX, since those came bundled with certain versions of SGI's entry level workstations (Indys, O2s). However, as another poster already mentioned, this was a very shoddy port, essentially just the MacOS version recompiled with a MacOS on Unix library. It looked and worked like the Mac version, was slow and unreliable and was completely out of place on a normal irix desktop. On top of all this, back in those days Photoshop wasn't "the" standard like it is today, it was just one of many image manipulation packages, and especially on Irix, there were quite a few to choose from.

      I have licenses for Photoshop, Illustrator and Premiere on one of my SGIs at home, as well as the now discontinued Eclipse, and Eclipse was miles ahead of Photoshop back then. I don't use any of the Adobe packages anymore, mostly because i find them totally awkward to use - significantly worse than gimp.

    7. Re:It's insanely too bad Adobe ported 1st to SGI by MROD · · Score: 1

      The main problem (at the time) of the Unix versions of Photoshop was the licensing cost. I remember at the time being stunned by the single-seat license being £1000 when the Macintosh version was less than a quarter of that. And they were the academic prices.

      Basically, Adobe (and to be fair a great deal of other companies) thought that if you ran UNIX then you should pay a heavy premium. Maybe they thought UNIX == BigCorporation(tm) and hence they could get away with the huge price.

      --

      Agrajag: "Oh no, not again!"
  26. This is news? by supabeast! · · Score: 2, Insightful

    So graphics professionals still aren't using GIMP because the interface blows and it doesn't support formats that have long been important in the professional world? Wow, I've never heard that before! Gee, next you'll be telling me that people don't use Blender because the UI is deplorably bad! Oh wait, I just realized that these topics have been getting regular coverage in the OSS communinity for years and it's not getting any better!

    People not using OSS because the UI sucks or because it's crammed full of useless widgets and oddball features nobody but the original programmers needed isn't a new phenomenon. It certainly isn't one that deserves continued discussion. We all know that the GIMP isn't really useful for anything other than simple image manipulation for the web (or creating tacky web graphics circa 1999.), we all know that Blender is only good for crazy people with limitless free time to spend trying to make the interface not suck, and that OpenOffice is more bloated than Oprah Winfrey. Why not just stop covering these crappy old products and start giving some attention to newer, better alternatives?

    1. Re:This is news? by Anonymous Coward · · Score: 0

      "Why not just stop covering these crappy old products and start giving some attention to newer, better alternatives?"

      I hope the answer isn't "because such alternatives don't exist"...

    2. Re:This is news? by roastedMnM · · Score: 1

      I don't mean to pry or be in any way offensive, but I still have a question: What newer, better alternatives?


      I would gladly try alternatives, but have found none.

  27. What about.... by dteichman2 · · Score: 1

    Cinepaint?

    Who gives a shit about the interface? You can always change it, or find someone who already did.

    --


    Silence is golden... and duct tape is silver.
    1. 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.

    2. Re:What about.... by Anonymous Coward · · Score: 0

      linux users might like to spend all day installing new themes, but the rest of the world prefers to just do their work and be done with it.

    3. Re:What about.... by Anonymous Coward · · Score: 0

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

      You must be new around here.

    4. Re:What about.... by Anonymous Coward · · Score: 0

      and want to do my damn work
      And that's best accomplished by reading slashdot!

    5. Re:What about.... by clawoo · · Score: 1

      Totally agree. When I work the last thing I want to do is manage the interface. As along as it stays the hell off in a corner, compact and not randomly grouped, it's good. When it spawns 12 damn windows all over the screen I feel I could curl up and die.

      --
      This is not your signature.
    6. Re:What about.... by Hosiah · · Score: 2, Insightful
      I do. I'm a professional, not a hobbyist, and want to do my damn work, not fuck around with the interface.

      What is it, exactly, that Photoshop does for you? Read your mind and draw the image on the screen while you sit back ten feet with your arms folded and meditate? So there's lots of little windows instead of one big one. So most of the functions are accessible with a right-click to the canvas. What's the big deal?

      Does this help to at least clarify some of why it's that way?

  28. Why GIMP isn't enough by typical · · Score: 2, Insightful

    Yes, there are some missing dead-tree output features. But honestly, you know why Photoshop gurus don't like the GIMP?

    It's the same reason I'd be pissed if you took all my POSIX utilities away. Or replaced emacs with Visual Slickedit.

    The user has spent a very large amount of time learning to use the incumbent software package very, very well. *Any* deviation in UI or featureset means that (a) he has to blow a lot of time relearning a tool and (b) he immediately notices missing features that he depends on, but it takes him a while to discover the things that the challenger can do, but the incumbent can't.

    The article mentions the relearning time, but I'd say that 90% of the problem has to be right there.

    User knowledge is the nicest of the forms of lock-in that I can think of (from a user standpoint). It's straightforward, it's comparatively easy to assess (the user knows how long it took him to learn a tool), you can't really hide it from a customer, and it never *can't* be overcome if absolutely necessary.

    --
    Any program relying on (nontrivial) preemptive multithreading will be buggy.
  29. Eeeeeeeveryone needs PS by ben_1432 · · Score: 2

    Right. Cause industrial-strength photo manipulation is at the core of every job, and we should all blow $1600 on Photoshop. While we're at it, everyone needs the full Adobe (and former Macromedia) suites too.

    The only thing this sort of survey shows is how much piracy goes on. There's no way in hell every kid under 20 has paid for PhotoShop, or Dreamweaver, or Flash, or all the other "must have" crap.

    1. Re:Eeeeeeeveryone needs PS by TubeSteak · · Score: 1
      There's no way in hell every kid under 20 has paid for PhotoShop, or Dreamweaver, or Flash, or all the other "must have" crap.
      No, but when those 'kids' move into the work force, they end up using a licensed copy of that software, or since it is all they know, they make a purchasing suggestion.

      This is why big name companies don't make a huge fuss over piracy. They aren't stupid and they know that their latest release is going to be cracked within days, if not sooner.

      Some kid downloading the latest patch/keygen/cracked exe isn't what hurts corporate bottom lines. Major companies focus on counterfeiters.

      When organizations & people buy what they think are legitimate copies of the software, the software writers lose.

      This is why MS, Adobe, Norton, etc etc etc focus their time on people pumping out faked retail packages.

      They know that a download doesn't necessarily = a lost sale... but (in their minds) every counterfeit bought can be directly tied to a lost sale.
      --
      [Fuck Beta]
      o0t!
    2. Re:Eeeeeeeveryone needs PS by Valar · · Score: 1

      I don't think you get it. If you survey a bunch of people about what they wish they could do on Linux, they aren't gonna answer "word processing", because the availible word processing applications are good enough. However, people DO wish they had photoshop, because currently there is a gap with what is availible in graphics apps on linux. The most commonly needed business desktop niches are filled (word processing, email, etc). Not everybody needs photoshop, but the people who do can't use linux.

    3. Re:Eeeeeeeveryone needs PS by ben_1432 · · Score: 1

      You make some very good points, I hadn't looked at it from that perspective.

    4. Re:Eeeeeeeveryone needs PS by ben_1432 · · Score: 1

      If you survey a bunch of people about what they wish they could do on Linux they'd probably say "the same stuff I do on Windows - browse the net, send emails, chatrooms, myspace, Google". All of which they can do on Linux.

      Why can't they run PS on Linux anyway? Isn't OSX based on Linux?

    5. Re:Eeeeeeeveryone needs PS by larry+bagina · · Score: 1
      1. Photoshop
      2. Autocad
      3. Dreamweaver
      4. iTunes
      5. Macromedia Studio
      6. Flash
      7. Quicken
      8. Visio
      9. Quickbooks
      10. Lotus Notes

      Do you really think it's a bunch of 20 year old pirates who "must have" Notes, Quickbooks, Visio, Quicken, or Autocad?

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    6. Re:Eeeeeeeveryone needs PS by NoMoreNicksLeft · · Score: 1

      Not just in their minds, that's a person who proved they were willing to buy it.

      And this sort of piracy should be illegal. I never had a problem with them cracking down on people who sold warez... nail the bastards.

    7. Re:Eeeeeeeveryone needs PS by Valar · · Score: 1

      Wish implies that they can't do it already. You don't generally wish for things you already have. Linux has web browsers.

      And no, OSX is not based on Linux. It is based on a combination of mach and BSD that mostly provides BSD-like functionality.

    8. Re:Eeeeeeeveryone needs PS by ben_1432 · · Score: 1

      Do you really think it's a bunch of 20 year old pirates who "must have" Notes, Quickbooks, Visio, Quicken, or Autocad?

      No. I think that just emphasises there's a pretty obvious overlap between what kids 'need' and what businesses use.

      With the exception of Autocad, the rest of the 'grown up stuff' are near-standard business tools.

  30. Huh? by Spy+der+Mann · · Score: 2, Informative

    Excuse me, but I nowhere read that. Just because dreamweaver was included in the list of possible ports, it doesn't mean that Linux users need it.

    Also, you took the tangent, instead of reviewing his points, you simply dismiss the whole argument because of something else he said.

    Let's analyse his points, ok?

    a) The menus - this may be fixed in 2.4, but it took a long time.
    b) The color space (CMYK) and depth (16-bit)
    c) The plugins

    To make GIMP plugins, you need to compile them. He says Photoshop isn't an application, but a platform. And I think he's right. The GIMP, as good as it is^H^Hwas, has stalled in the stoneage, while Photoshop has evolved.

    In my opinion, rewriting GIMP from scratch and making it extensible would be the best choice.

  31. Color support is lacking by davebgimp · · Score: 1

    I make magazines for a living and I find that Gimp is fine for your average web graphics but lack of CYMK support and an inability to manage and convert color profiles for print makes it pointless to use in my line of work. Also, PS has a much more powerful set of tools for image retouching. Honestly though... it's free. For what it is, the guys who made did a great job. I use it at home and would love to bring my office over to it, but since I don't pay for PS personally, I'm not too upset when the bill for 30+ licenses comes in.

  32. Gimps by Neo-Rio-101 · · Score: 1

    Gimp is only a semi-decent replacement for the home consumer Photoshop CS series.

    You also have to admit that the name "The Gimp" is somewhat risque as well, considering most people know what a gimp actually is.

    To a novice, Photoshop obviously must be a photo application. An application called "The gimp" does what exactly?

    --
    READY.
    PRINT ""+-0
    1. Re:Gimps by Homr+Zodyssey · · Score: 1

      You also have to admit that the name "The Gimp" is somewhat risque as well, considering most people know what a gimp actually is.

      What is risque about what a gimp "really" is? Perhaps you are referring to the man referred to as a gimp in Pulp Fiction?

      A Gimp is actually a person with a limp.... http://dictionary.reference.com/search?q=gimp

    2. Re:Gimps by Spazmania · · Score: 1

      An application called "The gimp" does what exactly?

      I dunno but it sounds pretty lame.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  33. Professionals and Professionals by Anonymous Coward · · Score: 0

    There are people who call themselves professionals. And there are real professionals. Like all generalities, the following truism should be taken with a grain of salt; but one good way to separate the wheat from the chaff is automatically disregard anyone who constantly whines about the fidelity of their tools. Real artists aren't constantly looking for scapegoats.

  34. photoshop killer? by moosesocks · · Score: 1

    How long before we see a photoshop killer?

    Personally, I think that PS is beginning to show its age, and that something with a more elegant UI and a lightweight codebase will take off and surpass photoshop in the next few years. For a start, Adobe could start using newer versions of the OS toolkits on Windows and Mac. Photoshop is one of the only remaining Carbon applications out there.

    After 10-15 years of existance, most programs begin to show their age. Although Photoshop has come a long way, I still feel like I'm using the same program that was out there 10 years ago with a few (okay, a lot) extras tacked on to it. It's a very bittersweet feeling that "This is great, but it could also be a lot better"

    Apple's aperture is a step in the right direction except for the fact that it's slow as hell and not cross-platform.

    The Gimp isn't great. A lot of it's held back by GTK which doesn't really seem well-supported on any platform (partly because it was written for X windows. eck.) I say that the developers cut their losses, and start over rewriting it with using the lessons learned while writing the old codebase. They can crossport the tricky image processing stuff, but everything else needs to go. If it hasn't gained acceptance by now, I think the problems are a lot deeper than surface-level.

    --
    -- If you try to fail and succeed, which have you done? - Uli's moose
    1. Re:photoshop killer? by Moridineas · · Score: 1

      Yes, you're absolutely right. Photoshop is one of the only major carbon apps left around.

      Let's see...except for Microsoft Office. Blizzard's world of warcraft. APPLE's iTunes. Hell, did I mention the FINDER. (and countless, countless others)

      Get with it, Carbon alone is not a reason to criticize a program.

    2. Re:photoshop killer? by Builder · · Score: 1

      I don't know about aperture because I've not used it, but lightroom ROCKS. It has cut my post-processing time in half on any given batch of pictures. It becomes where I do most of my work, and then just finalise in PS CS2.

    3. Re:photoshop killer? by melekzek · · Score: 1

      IMHO, v7 was the best PS version. Its all downhill after that. Try doing the same thing in v9 and v7. v7 uses less memory, and is a lot more responsive. After using v9 for a while, v7 just flies. I know a lot of people who use v7 for most of their work, and v9 only for some specific things (e.g. more tools support 16 bit, a bunch of new tools such as shadow/hightlight, warp, etc)

    4. Re:photoshop killer? by Quarters · · Score: 1
      Personally, I think that PS is beginning to show its age, and that something with a more elegant UI and a lightweight codebase will take off and surpass photoshop in the next few years

      Like what? PhotoPaint didn't fit the bill, neither did PaintShop Pro. Design professionals could care less about intangibles like "lightweight codebase". They care even less for different UIs because they've already spent the time and money to learn the current UI.

      For a start, Adobe could start using newer versions of the OS toolkits on Windows and Mac. Photoshop is one of the only remaining Carbon applications out there.

      Adobe has been steadily moving all of their applications to the QT toolkit for the past couple of years. Choosing Carbon over Cocoa is a moot point for them because it still leaves them in the position of having to write a completely different GUI system for Windows or any other platform they might support.

  35. I can't resist... by joNDoty · · Score: 2, Funny

    "GIMP should be enough for anybody."

    ::ducks::

    1. Re:I can't resist... by Freedryk · · Score: 1

      Oh, so true, so true!

  36. Um... by happymedium · · Score: 1

    You know any idiot can get GIMP on Windows by running two .exe's...

  37. Equality != Identity by tverbeek · · Score: 1, Insightful
    A student at the art-and-design college where I work recently made a suggestion for how we could save some money on software licensing, so that the funds could be spent on other things. Great idea. Ideologically, I couldn't agree more. But I had to argue that it wasn't practical.

    He was suggesting that we use OpenOffice instead of MS-Office, but one of the biggest problems is that OOo-Writer simply isn't MS-Word, and OOo-Impress isn't PowerPoint. Even if they were feature-compatible (which they're not quite), they still wouldn't be identical, and a substantial percentage of users (faculty and students) can't deal with having Feature X on a different menu than it is in Word. Me... I can deal with WordPerfect and MS-Word and OOo-Writer each doing things differently from the others. And I can manage moving from the GIMP to Photoshop to Fireworks, much like I can move from OS X to Windows to Linux. But I gain that flexibility at the expense of efficiency and proficiency. For a professional for whom the latter two factors are of greater importance, the "just as good as" argument isn't going to be very persuasive.

    --
    http://alternatives.rzero.com/
    1. Re:Equality != Identity by dbIII · · Score: 1
      they still wouldn't be identical
      Obviously.
      can't deal with having Feature X on a different menu than it is in Word
      Those people will also have problems with the next version of Word - I've seen that a few times. We really are teaching people how to use software in the wrong way - or leaving them to fend for themselves so they just push buttons to do tasks and if someone moves the buttons they are of little use in their jobs. Proper training prevents those road trips to see angry clients that have forgotten their MS Windows username (which matches their real name) but cannot respond with anything other than "the network is broken" to any question due to anger and frustration.
    2. Re:Equality != Identity by killjoe · · Score: 1

      "For a professional for whom the latter two factors are of greater importance, the "just as good as" argument isn't going to be very persuasive."

      FOr a decade or more SQL server is/has-been inferior to Oracle. Everytime a flamewar flared up on usenet the MS fanboi crown always sang this tune. "It's good enough, it does what you need, you don't need those extra features, and it costs a hell of a lot less".

      So there you go. Open office is not as good as MS office but it costs a hell of a lot less. It's up to your administration, CIO, CEO or whatever to actually justify paying for MS office when there is a product almost as good for free.

      Some people are able to justify that, more and more people are realizing that they can't.

      Before you bring up re-training and compatibility just remember your people will need to get re-trained at every upgrade of office and they will lose compatibility as well.

      --
      evil is as evil does
  38. Linux is more advanced - because the users are by Anonymous Coward · · Score: 0

    I get people asking me how I do a certain effect or edit all the time, and I love to watch their face when I start telling them about Linux and the software I use. These are professionals who spend 5000+ on their kit and I do much MUCH better
    using free software tools. The reason (without wanting to sound arrogant) is simply that I know what I am doing. All the money these guys spend on expensive windows and mac software is fine, but the tools don't make the artist. Things like
    photoshop get labled as 'professional' tools because they make difficult things easy to do, too easy maybe. I have to sit down and work out what I am going to do with more care, but then I seem to get a vastly superior product at the end of the day, maybe because I am not relying on fancy software to do things for me but actually understanding what I am doing and why. Free software still requires that you think, it gives you access to unimaginable power if you understand the problem domain and the interface, but it's not for lazy 'professionals' who just want quick impressive results with lots of 'wow factor'. A real artist needs serious tools.

  39. The study must have been stuffed. by twitter · · Score: 1
    So, the author is telling me that Photoshop is the most important app for Linux Desktop Migration? He tells me this right after telling me that the only people who really know how to use it are graphic design users on Macs, aka a minority of a minority of computer users? He admits that he's out of his comfort zone when it comes to graphics. What he should realize is that most of the people he knows are like that too and are better served with something that does not cost $4,000 a seat per year. The very simple tools provided by Digikam, kpaint, and konqueror are all the average user needs. GIMP is overkill for the majority of computer users. He and Novel have been trolled.

    Would I be happy to see Adobe bring all their toys to the GNU/Linux party? Sure. Does more than 1% of the population need it? No.

    GNU/Linux desktops have what users want and more. People who don't think so have not tried to use it in the last six years.

    --

    Friends don't help friends install M$ junk.

    1. Re:The study must have been stuffed. by Jack9 · · Score: 1

      10% or more of the users at every place I have ever worked, have needed it. That's a great deal more than 1% of the paying userbase. When you're counting pre-installed, the % dwindles, but MS isn't getting money for additional products (Office, MSSQL, etc) from them in anyways (in the abstract sense).

      --

      Often wrong but never in doubt.
      I am Jack9.
      Everyone knows me.
  40. The real reason ... by Mirzabah · · Score: 1

    .. is the stupid name and godawful logo.

  41. Taught Gimp lately?? by deathguppie · · Score: 2, Informative

    Lets face it. Graphics is about art, not software. Artists use the techniques and software that they have been taught to use. I use Gimp because the artist part of my software experience came after my debut in linux. Had I gone through any graphics program, I would undoubtedly be using Photoshop. Why?
    Because that's what they teach. Why would I want to relearn another peice of software??

    If you want people to use your software, you have got to get it used in schools. Just my two cents.

    --
    once more into the breach
    1. Re:Taught Gimp lately?? by paintbrush12 · · Score: 1

      Gimp is loaded on EVERY linux computer at savannah college of art and desing . i use it occasonally . but it is usless for HDR, 16 and 32 bit image editing . and it's cumbersom. it also dosn't have half the features that photoshop does . automated phtotmerge . raw image handling , not nearly enough filters . and ther are other HDR and stiching softwares avalable for linux for free.

    2. Re:Taught Gimp lately?? by Valar · · Score: 1

      "Lets face it. Graphics is about art, not software."

      True, but you have to consider something: I need a piece of software that has all the right tools to make my art. Gimp is lacking features I need to do my graphics. Firstly, I need some degree of monitor to print calibration. I need 16 bit support, since a lot of the images I work with come straight from a digital SLR. I need pantone support, because I work with a variety of different processes and shops. I use a couple of photoshop filters for which no GIMP equivalent exists (I would be pleasantly surprised to find NoiseNinja for Gimp).

      In summary, editting is only one phase of my workflow. I'm the only one who sees my work on a screen. I need a powerful set of tools for making sure it translates into physical media too.

  42. Gimp is good enough by Stalyn · · Score: 4, Interesting

    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
    1. Re:Gimp is good enough by MechaStreisand · · Score: 1

      I checked out that link, and I noticed something really odd: the reporter says that Linux distributions can't include mp3 players because the patents on mp3 make it incompatible with the GPL. What the fuck are they talking about? The GPL doesn't apply to software that runs ON Linux, only to stuff that links directly to the kernel. It's perfectly legal to distribute non-GPLed software along with Linux, and it's not the GPL that would make it illegal to distribute patented software, but rather the patents themselves.

      --
      Disclaimer: IANAL. This post is, however, legal advice, and creates an attorney-client relationship.
    2. Re:Gimp is good enough by Stalyn · · Score: 1

      It might have to do with LAME. I'm not really sure. But I think the problem is the distribution of binaries and not paying licensing fees. If anyone can clarify this I'd like to know.

      --
      The best education consists in immunizing people against systematic attempts at education. - Paul Feyerabend
    3. Re:Gimp is good enough by Anonymous Coward · · Score: 0

      But then again how many photo professionals use Linux in the first place?

      Probably few, what with the poor state of photo editing software on Linux. What? You mean you choose your OS and THEN your apps? How quaint.

    4. Re:Gimp is good enough by Stalyn · · Score: 1

      I think the immediate goal for the Linux desktop is to fill the needs of the average computer user. These things include Email/IM/Web/Media Management, I think that covers about 70% of the desktop market. Right now Linux does the majority of these things pretty well. It just needs a little tweaking and some better "packaging" by which I mean marketing/usability/setup and support. To focus your efforts on a small percentage of users is just not the right way to go. It's better to grab the ordinary users and then use them as an incentive to get niche apps ported to your OS. Sure you could spend your limited resources on making Linux accessible to photo/video professionals but it makes more business sense to work on things like better ipod connectivity.

      --
      The best education consists in immunizing people against systematic attempts at education. - Paul Feyerabend
    5. Re:Gimp is good enough by Anonymous Coward · · Score: 0

      What you say may be true but your initial argument of "how many graphics artists use Linux in the first place" is still a backwards way of looking at the situation. They CAN'T use Linux because they lack a good image editor. Business sense or otherwise.

      Another thing to consider is whether or not Linux is developed on "business sense" -- it seems it might be done more by what one feels like doing (or needs) at any given time. Moreso than any other OS, but not always, I concede.

      Sorry about the conceited "how quaint." That was rude of me. :-(

    6. Re:Gimp is good enough by prudek · · Score: 1

      My girlfriend has been using Linux and GIMP for professional photography for three years now, with quite some business success.

    7. Re:Gimp is good enough by poot_rootbeer · · Score: 1

      The Gimp is good enough for most of us.

      Most Of Us aren't graphics professionals, though. And why should we ever settle for "good enough", anyway?

  43. 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 miro+f · · Score: 1

      this must be one of the few known cases of software piracy actually helping the company. I could imagine how the userbase of Photoshop would suddenly dramatically decrease if suddenly all the pirated copies disappeared, suddenly people would start using free alternatives rather than plonk down $2,000 for photoshop.

      I'm sure then we'd start seeing courses on The GIMP and more money going into improving its feature set

      I'm sure the best thing Adobe can do is allow the piracy to continue.

      --
      being vague is almost as cool as doing that other thing...
    2. 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.

    3. Re:Gimp would get a lot more popular if... by John+Harrison · · Score: 1

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

      I would guess that they have actively decided to not implement effective anti-piracy measures. If people are going to pirate software you want to make sure that they are pirating your software. That is how you maintain your place as a standard. If everyone who currently pirated PS suddenly switched to GIMP that would be a very bad thing for Adobe. Don't think that Adobe doesn't know this.

    4. Re:Gimp would get a lot more popular if... by coaxial · · Score: 1

      They'll never lock down photoshop they way you're thinking (e.g with dongles and such). Adobe likes the fact that photoshop is pirated. It means people use it. These same people will eventually need to do something legit, and when they do, they'll want to use photoshop because that's what they know. And then they'll shell out 1000 bux or whatever for it.

      Like they saying goes, "the first one is always free."

    5. Re:Gimp would get a lot more popular if... by foxwitt · · Score: 1

      Yeah, that's part of what I was getting at, but I didn't make it very clear. I meant that the increased popularity and use would come mainly from the average user who has a pirate copy of Photoshop sitting about, not from the professionals whose company buys the program for them, and for whom the GIMP simply won't cut the mustard.

      I do think you're right on about the free exposure that Adobe gets from all the pirate copies, as well. The average user is never going to pay full price for Photoshop, but it's by far the most popular photo-editing program out there, so that's the one everyone wants to get. If they see a pirated version of Photoshop vs. a free version of GIMP, nearly everyone goes for Photoshop on name recognition alone.

      --
      Today our lesson will be Chapter 1 of Elementary Necromancy: Proper Use of a Shovel.
    6. Re:Gimp would get a lot more popular if... by ipfwadm · · Score: 1

      If they see a pirated version of Photoshop vs. a free version of GIMP, nearly everyone goes for Photoshop on name recognition alone.

      And even if they DIDN'T recognize the Photoshop name, which do you think they would choose, based on name alone? "The GIMP" has to be the worst name for a product in the history of the world. I'm embarrassed to even say it if someone asks me what software I used to make an image.

    7. Re:Gimp would get a lot more popular if... by ipfwadm · · Score: 1

      rather than plonk down $2,000 for photoshop.

      Whoa... Are people scalping Photoshop on EBay now? The full version of PS is $650. Adobe's entire Creative Suite (PS, Acrobat, Illustrator, InDesign, and GoLive) is still "only" $1200.

    8. Re:Gimp would get a lot more popular if... by Mr.+Hankey · · Score: 1

      I know a fair number of people who would likely choose GIMP given this choice, creative types being what they are. If you're a Mac user, you might remember the old name of mpegger. The GIMP's a lot better than it used to be, having used it since the static Motif binaries they distributed so long ago. No doubt most people's issues will be resolved over time. Once the developers have itegrated the core with littleCMS or something like it, and brought CMYK support up to the level of at least the current RGB support, you'll probably see a lot more people using it.

      --
      GPL: Free as in will
    9. Re:Gimp would get a lot more popular if... by netcrusher88 · · Score: 1

      Which is precisely why Photoshop will never have stronger piracy protection, and why no one is ever sued for an illegal copy of Photoshop, even though, as parent points out, almost no home user ever buys a license. It's an ingenious business plan: don't bug people who d/l Photoshop. They wouldn't buy it anyway, they'd buy or d/l inferior (or at least cheaper) software. However, they will go to their employer and demand that they get Photoshop. The business will have to buy licenses, and thus Photoshop makes its way around the industry, one corporation at a time. And employees get hooked, and when they move on, their addiction follows them to their next employer. Viral marketing at its finest.

      --
      There's an old saying that says pretty much whatever you want it to.
    10. Re:Gimp would get a lot more popular if... by Skuld-Chan · · Score: 2, Insightful

      I would say Adobe does care - otherwise they wouldn't have put activation into the product.

    11. Re:Gimp would get a lot more popular if... by Anonymous Coward · · Score: 0

      there's also desktop methods to consider. The SPA recognizes one CPU active copy as do most publishers. For a time Quark and other apps would sniff for matching serials across networks but would not prevent multiple copies from running. Considering I have a portable computer that goes with me for onsite clients and my main tower at home this is no small godsend.

      I also tend to keep an active pirated copy to reinstall. After 3 iterations of purchsed "upgrade" versions, I tend to balk at fumbling 4 sets of cd's to re-install my latest version on the backs of all the others. Yech. Of COURSE I use the single installer .pkg and get back to work. I have the stupid piece of paper in the pile of boxes in storgage if the auditor wants to waste an afternoon helping me dig it out.

    12. Re:Gimp would get a lot more popular if... by Al+Dimond · · Score: 1

      I wouldn't call it rare for piracy to help a company. If what I read on Slashdot is true, Microsoft was pretty permissive about people installing early versions of Office from work onto their home computers. How many households with multiple computers actually have proper licenses for all the copies of Office and Windows they run? Many computers sold with WinME are still in heavy use and running XP five-finger-discount edition these days. You think Microsoft would rather those computers be running something else?

    13. Re:Gimp would get a lot more popular if... by Rakishi · · Score: 1

      Cut the prices in half if you get the educational version, possibly even less if your unviersity has a deal or something along those lines.

    14. Re:Gimp would get a lot more popular if... by Anonymous Coward · · Score: 0

      Actually, CS2 has a fairly decent protection (nothing like the 4.x days that relied on simple multiplications with constants and the right prefixes).

      But regardless, you're still wrong. Even if we couldn't pirate PS so easily, most people still WOULDN'T go for GIMP. Why? Because there are still loads of alternatives which are arguably better like Corel Painter, Corel Paint Shop Pro (VERY well known and LOTS of people love the interface even better than that of PS) Photoshop Elements (much cheaper), MS' Digital Imaging Suite (I'm not a fan but it seems to sell quite well), older versions of Photoshop (like sometimes ship bundled with some P&S digicams -- an old Coolpix came with PS v4.0), etc.

      Pros will stick to Photoshop no matter what. Switching to something else means lost productivity (at least in the learning stage) and profits. Where I work there about a dozen photographers sharing some photo workstations (all using PS). They all know it in and out. If someone needs help with something there's always someone that knows. You hire someone new or temporarily, they know the app already (and there are loads of VERY good books as well as great training videos by Total Training, Lynda, VTC, etc). It works great, has all the features they want, etc - well worth the price.

      GIMP lacks in many ways (not just the interface which is already a HUGE issue): 16bit and CYMK are common issues that everybody mention. Features! GIMP has perhaps most features from PS 4.0 but it's NOWHERE near the features of CS2. There are also the issues of color calibration and color workspaces. Handy commercial plugins and actions. Integration with the other apps in their Adobe Suite (illustrator and premiere namely). Adobe Camera RAW. This list could be much longer...

      And that's assuming we're talking about GIMP on windows -- not on Linux like they're mentionning in TFA. You might have a slight chance to switch ~0.01% of pros to GIMP, but to GIMP on Linux? That'll be a million times harder.

      That means Extensis Portfolio [digital asset management] won't work. That means Extensis SuitCase [font management - typography does matter] won't work. That means RAW converters won't work [Nikon Capture, CaptureOne, Fuji RAW EX, Adobe Camera RAW, Canon's, etc]. That means our color calibration tools [MacBeth, Monaco, etc] won't work. That means our existing/preferred pano/QTVR tools won't work. That means that our nice noise removal tools won't work. That means most of the little everyday programs [ACDSee, QImage, Bibble, BreezeBrowser, Nikon View, Silverfast, VueScan, ETC!).

      That implies a TOTAL change of ALL apps for new apps that DON'T EVEN EXIST (there might be some tools that offer partial functionnality but they won't cut it much like GIMP doesn't - don't bother making a list). That means having to learn using a new platform/OS ("Where's my C: drive?"), as well a dozens of specialized applications (that have no replacements/equivalnts). That means a new entire workflow.

      That's almost like taking away all of a carpenter's power tools, or taking away C++, Perl and Java from programmers and giving them GWBasic in replacement ("What do you mean it's not good enough?"). You can't really do that... People would rather quit than have all their valuable tools taken away from them.

      Right now, Linux + GIMP is NOWHERE good enough for pro use. And even for basic home users with basic needs, the most part would rather use something like Paint Shop Pro, Picasa or Paint.NET WAY before GIMP. Whoever says GIMP is good enough just doesn't have a clue, perhaps they should try something else for a change - and hopefully they'll see the light...

      I've actually paid for my version of Photoshop, believe it or not.

    15. Re:Gimp would get a lot more popular if... by advocate_one · · Score: 1

      ah yes the "educational" version... which if you read the eula carefully you will discover that you are only licensed to use it while you remain a student and also you are not allowed to do paid work with it...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    16. Re:Gimp would get a lot more popular if... by RedBear · · Score: 1

      Gimp would get a lot more popular if... If Adobe figured out some way to lock down Photoshop so that it couldn't be pirated as commonly as it is currently.

      That's exactly what they've been doing recently with their "software activation" initiative. Same with Macromedia, only they call it "product activation". Now instead of borrowing someone's CD for an afternoon you'll have to find a cracked version online somewhere. Makes it much more difficult for the common user to pirate it. Everything later than Photoshop 7 for Windows and CS on the Mac requires activation, and can't be activated with the same serial number more than once or twice. It's really pretty effective.

      Oddly enough a lot of people are still going to go through all the trouble of finding and downloading a 300MB cracked version of Photoshop rather than using the GIMP. And if they don't know how to get the cracked version they will buy Photoshop Elements for $79 rather than using the GIMP. That's how bad the GIMP sucks, according to your average user. So no, I don't think GIMP is going to get more popular until it improves a LOT. GimpShop is merely a very small step in the right direction. Another great step would be to stop calling it the GIMP. That name is absolutely infantile and sounds totally ridiculous in non-geek circles.

      Every year since 1998 or so was also supposed to be the year of the Linux desktop, but that hasn't happened either. There are reasons for this, people, whether you understand them or not.

      OpenOffice.org is the same way. People only use OO.org when they have no way of obtaining Microsoft Office on the cheap. Either that or they are idealists. The only reason Firefox has taken off as fast as it has is because it has some great killer features that make the average person's life easier, e.g. ad blocking, popup blocking, tabbed browsing and many great extensions. If Firefox was still as rough as OO.org, the GIMP, and Linux in general, nobody would be using it. This whole idea of Linux or other open source software projects taking off like wildfire because of some external event is going to remain a pipe dream until our software gets a hell of a lot more polish. I say this as a person who has used Linux as a desktop, used OpenOffice.org and used the GIMP.

      You'll know when these things no longer need to be drastically improved because you'll wake up one day and everyone you know will be using them. It's that simple.

    17. Re:Gimp would get a lot more popular if... by cortana · · Score: 1

      If they *really* cared then they'd implement something much harder to hack around--they could license Starforce for insteance.

    18. Re:Gimp would get a lot more popular if... by tigersha · · Score: 1

      And Photoshop Elements, which is still better than Gimp and definitely does the "Good Enough for Most People" thing is only $70. I have 2 copies, one I got for free with my scanner, one with my printer. Actually, PS Elements is the reall competition to Gimp

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
    19. Re:Gimp would get a lot more popular if... by commodoresloat · · Score: 1

      Exactly. And easily pirated photoshop keeps kids away from learning the gimp, so when they do get jobs at high profile graphics outfits they will ask their employers for copys of photoshop on their workstations rather than saying "ah, don't bother spending the money, I prefer to use the gimp...."

    20. Re:Gimp would get a lot more popular if... by DrXym · · Score: 1
      If Adobe figured out some way to lock down Photoshop so that it couldn't be pirated as commonly as it is currently.

      A simple way would be to watermark all images until you register the product with a valid serial number. Aside from degrading the image quality, it would assist in tracking you down, should you be so foolish as to web up anything you created with your illegal installation.

    21. Re:Gimp would get a lot more popular if... by Rakishi · · Score: 1

      The first part makes sense, the second is interesting although I'm not sure if it is true. The Photoshop EULA (as on the adobe webpage) only says you need to qualify for the educational version to use it, and mentioned nothing about for-profit work. There is no separate EULA listed for the educational version, simply one paragraph in the regular EULA. All google searches likewise give no actual evidence of this restriction.

      I'd be interested in knowing if it is actually true or not.

    22. Re:Gimp would get a lot more popular if... by Anonymous Coward · · Score: 0

      Probably they don't want a malwarish piece of bloatware slowing down the performance intensive work a graphics app like Photoshop often does.

    23. Re:Gimp would get a lot more popular if... by kevingolding2001 · · Score: 1
      You're forgetting 'Elements'.
      A legit, fully licensed copy of Photoshop Elements is given away free with pretty much every high end camera sold these days. I used to struggle away with Gimp, but when I bought my EOS camera, I got a copy of Photoshop Elements, and suddenly I was basically just "getting the job done" instead of wrestling with the stupid Gimp interface.

      Maybe the Gimp would get a lot more popular if it was included free with high-end digital cameras. But then again, maybe it would just piss off more people who are used to simple "just get the job done" interfaces.

    24. Re:Gimp would get a lot more popular if... by gEvil+(beta) · · Score: 1

      Copies of Photoshop that are licensed to educational institutions via their volume license programs very explicity state in the (separate, signed) contract that they are to be used for classroom and educational use only and are by no means allowed to be used for production work. Also, the EULA for all versions states that a licensed user is allowed to install a second copy on a laptop or home computer, but that both copies cannot be used or run at the same time.

      --
      This guy's the limit!
    25. Re:Gimp would get a lot more popular if... by ipfwadm · · Score: 1

      "MPecker" kind of makes me chuckle. "The GIMP" makes me cringe.

    26. Re:Gimp would get a lot more popular if... by Mr.+Hankey · · Score: 1

      No accounting for tastes, now is there? :)

      --
      GPL: Free as in will
    27. Re:Gimp would get a lot more popular if... by miro+f · · Score: 1

      US$1200 is still about $2000 here (Australia)

      Either way, it's still a lot more money than the average joe is willing to spend to remove the red eye from their digital photos

      --
      being vague is almost as cool as doing that other thing...
  44. The bottom line, from the context of TFA. by soulctcher · · Score: 1

    The bottom line is that GIMP is different; it's not comfortable. YES, you can do almost everything in GIMP that you could do in Photoshop. YES, you can make it look like Photoshop. The largest problem with all of this is that you must WORK and you must CHANGE to do these things.

    Correct me if I'm wrong, but isn't comfort "comfortable" for a reason? People don't WANT to work. People don't WANT to change. It's not comfortable to do so.

  45. 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 PenGun · · Score: 0

      CMYK is just the inverse of RGB. The only reason it's a problem is that photoshop uses Pantone and it's a standard print standard and most colors that are printed are defined by it.

        This is the lever the established print world uses to make applications that do not subscribe to the Pantone color scheme useless. Only in the print world does this apply and that's why the Gimp does so well in web applications.

        The morons that claim anything that is not Photoshop is too wierd for them are just that ... morons.

    2. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      You're illustrating my point far better than you realize. Converting RGB to CMYK in a digital graphic has NOTHING to do with the Pantone Matching System. That's an entirely different issue.

    3. Re:Perfect example of OSS problems by mveloso · · Score: 1



      Your ignorance is showing! Who's the moron now? Heh.

    4. Re:Perfect example of OSS problems by vga_init · · Score: 1
      Okay, so one feature is missing from one piece of software, and now the entire OSS movement has lost its credibility to "professionals" such as yourself?

      I take your sentiments as a very positive sign, because your ferocity suggests to me that you have a genuine desire to see OSS succeed in the areas you've mentioned.

    5. Re:Perfect example of OSS problems by Tim+Browse · · Score: 4, Interesting
      CMYK is just the inverse of RGB.

      Thanks. That was a bloody good laugh. If you'd wanted to prove you have no clue about real world colour management and are, in your own words, a 'moron', then congratulations - you just passed with flying colours.

      Seriously, learn something about the subject before you spout off.

      As a starter for ten, show us your RGB -> CMYK and vice versa conversion functions, if they're "just the inverse".

      Hint - consider the information lost when converting from CMYK to RGB. If that's too taxing, think about the Key component.

      (Supplementary question - Photoshop is largely a bitmap editing application - guess how many people edit bitmaps by defining the Pantone colour used for each pixel. As other people have said, Pantone is a small part of the equation.)

    6. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      Honestly, I don't much care whether either Linux or GIMP is successful. OSS isn't a religious thing to me, so I don't have any emotional investment in it. The free/open source model works for some things, but I have serious doubts about whether it'll ever work for everything. If it does, that's great. I get free software that's as good as what I'm using now. If it doesn't, I already have tools that work and a commercial software market that understands how to supply better tools in the future.

      As for your first comment, you lead me to believe that you just don't "get" what this "missing feature" is. It's not just another item on a checklist. There is a chain of tasks that has to happen in order to get a graphic to an imagesetter. Converting a graphic from RGB to CMYK MUST happen for the job to be done. Otherwise, the file is useless to someone doing print work. No matter how good the rest of the software is, it is worthless for professional printing purposes without being able to do this.

      And, yes, the fact that people keep saying that GIMP is perfectly good enough for something -- when I KNOW that it just won't work for this purpose -- tells me a lot about the credibility of the development model. Too many of its proponents spew ignorant puffery that would put MS to shame. There are some very good developers doing good work in OSS, but there are way too many people who are willing to pontificate about things they know nothing about.

      David

    7. Re:Perfect example of OSS problems by Theatetus · · Score: 1

      Actually, his claim is a really good description of the difference, if I'm reading him right. I don't think he meant "inverse" in terms of a mathematical inverse; he meant "inverse" in the sense that one scheme describes light absorbed and the other describes light emitted.

      --
      All's true that is mistrusted
    8. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      You've apparently never met some of the aggressive OSS advocates that I have. They don't listen. They just insist that a tool does something that it won't do, because they're ignorant of what the actual NEED is. Those sorts of people try desperately to shove something onto you. You might not understand this little thing called a metaphor. Look it up sometime. I don't think a reasonable person could come to the conclusion that I'm a moron from anything I've written here, so I'll conclude that you have a problem with either reading comprehension or basic logic. David

    9. Re:Perfect example of OSS problems by Prune · · Score: 1

      That's wrong: RGB are not the primary colors of light, but the locations of the peak sensitivities of cones in the retina. It is something determined by physiology, not physics. What you should have said is that RGB are the additive primary colors, whereas CMY are the subractive.

      --
      "Politicians and diapers must be changed often, and for the same reason."
    10. Re:Perfect example of OSS problems by bigpat · · Score: 1

      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.

      The problem isn't geek arrogance, there is a chicken and egg problem. Commercial companies are only going to make software if they now people will be able to use it.

      Some people don't need photoshop and some people do. Let the ones that don't move to Linux and maybe photoshop will be ported later.

      Linux works as a desktop for internet applications and now since OpenOffice 2.0 it has an excellent productivity suite. GIMP is lacking in some areas, but is usable for most basic image manipulations (I actually use it on windows since I don't have photoshop). Really I think you have to look at Linux Desktop in terms of what applications are needed and why, and then make a decision. But it isn't going to please everyone.

      Monopoly just isn't healthy in the software business. If even 5-10% move from Windows to Linux and Apple continues to be a viable alternative (even Sun is still hanging on in some corners), then that is a good thing for everyone. Besides, I don't think serious photoshop users make up even that big of a percentage. That isn't arrogance. I am just saying that you have to work with what you have and push your strengths rather than dwell on the weeknesses.

    11. Re:Perfect example of OSS problems by PhunkySchtuff · · Score: 3, Informative

      Look, the lack of CMYK isn't the show stopper that it once was. Many modern workflows use RGB images throughout and have a colour-managed approach to conversion to CMYK that only happens just before the final output stage (be that to PDF or to an image/platesetter)
      There are many advantages to an RGB workflow - smaller image sizes and easier for software to work with is one, less RAM and disk space used, less data to crunch etc.
      Using a fully ICC profiled workflow, from capture/acquisition through retouching and editing and finally to output means that the one source image can be retargeted at a number of different output devices and keep the highest possible quality. The days of using pre-separated CMYK images are drawing to a close, as once you've converted to CMYK you don't want to go flipping back and forth between that and RGB. Also, once you've got CMYK, you will find it very hard to use the same source image for, say, printing on newsprint at 75lpi and printing the same image in a glossy magazine on high-brightness stock at 175lpi, or using stochastic screening...

      Anyway, having said all that, I totally agree with you that the GIMP is totally unsuited to a professional workflow.
      Time is money, and the time you waste with GIMP over a couple of weeks will easily cover the purchase price for the entire Adobe Creative Suite where you have a heap of apps that all work together and, more importantly, are recognised in the industry as having proven themselves to work...

    12. Re:Perfect example of OSS problems by Lobais · · Score: 1

      Gimp can't implement cmyk because of patent issues, but you can grab it as a plug-in: http://www.blackfiveservices.co.uk/separate.shtml

    13. Re:Perfect example of OSS problems by PenGun · · Score: 0

      Children there is no real need to be so angry. Pantone is the way most professional printing gets done. When the ink meets the mag it's Pantone colors almost exclusivly.

        Photoshop final output can be Pantone complient, because they have licensed the color scheme. Gimp output is 24 bit (total) and one could come close but Pantone rules the commercial world.

        Of course CMYK is not Pantone but Pantone is a printing color scheme and CMKY is for printing only, well in the digital world anyway, and Photoshop has a huge advantage if it's output prints transparently.

        Photoshop weenies are users and should be accorded the respect and consideration given to users. They do pay the bills after all.

        Do the right thing succkha: Bootsy

            PenGun
          Do What Now ??? ... Standards and Practices 1

    14. Re:Perfect example of OSS problems by DavidinAla · · Score: 2, Informative

      Try sending an RGB photo placed in a QuarkXPress document to a printing company and tell them that it doesn't need to be converted to CMYK. For all practical purposes, CMYK IS still an absolute must. :-) You're right that you don't want to convert back and forth between the two color spaces, which is why I edit and save an RGB before I save a different file as a CMYK. There are so many possible uses for the picture (even as CMYK) that I prefer to keep something as close to the original as possible. But when it goes to print, it's CMYK and converted to the proper size and resolution. David

    15. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      If Photoshop is ported to Linux, it won't be an OSS application, so my criticism won't apply to it. Photoshop on Linux would be a mature piece of software that has years of knowledge of how graphic artists work built into it. GIMP just doesn't have that, at least not to the extent that many professional users MUST have.

      As an aside, though, I DO think there is a lot of arrogance involved. Time after time, I see geeks confidently assert things about software which I know isn't true, simply because I understand the subject matter of the application better than he does. He understands software development better than I ever will, maybe, but he doesn't understand the needs of the end user, in too many cases. I'm afraid this tends to be more true in the OSS world than in the commercial software world, simply because of the financial incentive that the commercial people have to produce a product that people are willing to pay for.

      I certainly don't want to live in a monopoly software world. I'm not trying to argue that choice is bad. (I'm a Mac user, so I obviously don't mind being a part of a minority.) I'm not arguing that one or two vendors in ANY area is a good thing. I'm just pointing out why it's difficult for the OSS world to get things right in areas outside of geekdom.

      David

    16. Re:Perfect example of OSS problems by dbIII · · Score: 1
      software such as GIMP or just insist that it IS good enough for professionals
      It depends entirely on your profession doesn't it? Your profession requiring CMYK support is obviously not what they are talking about - but web graphics and general purpose illustrations for distribution in an office is a different story.
    17. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      You are correct, but I think anybody understood what I meant. I don't see any reason to get into a discussion of the difference between addictive and subtractive color. This didn't seem like the place to try to explain that, and it wasn't necessary to the point.

      David

    18. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      You really don't seem to understand. I can produce an entire ad or publication or whatever without EVER using Pantone colors. The Pantone Matching System is only used when a) an ink manufacturer produces a specific ink that matches a shade that Pantone defines, OR b) someone needs to produce a specific color match with CMYK, such as for backgrounds or type color or something similar. Pantone colors NEVER have anything to do with converting RGB to CMYK. David

    19. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      I believe I made it clear that I was talking about using GIMP for graphic arts in the printing industry.

    20. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      I think the title at the top of the page you're referencing makes it clear why this isn't really ready for serious use in a production environment. Note the word "rudimentary" in the following sub-head.

      "A plugin providing rudimentary CMYK support for The GIMP"

      David

    21. Re:Perfect example of OSS problems by PenGun · · Score: 0

      "Pantone colors NEVER have anything to do with converting RGB to CMYK"

        Yup true enough. You should, however, remember it is "ink" that is used to print.

        It's instructive to spend some time in a 'dark room' as well eh'.

            PenGun
          Do What Now ??? ... Standards and Practices !

    22. Re:Perfect example of OSS problems by Kelson · · Score: 1

      Strangely, I've never heard anyone claim that GIMP *was* sufficient for graphics arts in the printing industry. I take it your experience differs?

    23. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      I routinely have Linux advocates tell me that GIMP is a complete substitute for everything Photoshop does. I realize that these are just armchair experts, but there certainly are a lot of them. Even many of those who have used GIMP don't understand why it's not correct for use in the printing industry. They might have played with it enough to know that you can edit photos or whatever, but they don't understand what's neceesary for professional printing. I don't really blame people for not understanding such a narrow specialty, but it gets tiring having them tell me with certainty that I'm wrong about GIMP not being a perfect replacement for Photoshop for MY uses.

      I'm sure that some of the developers of GIMP at least have an understanding of some of the limitations of their product, but I also doubt that they really see the limitations from the viewpoint of an end user in the print industry.

      David

    24. Re:Perfect example of OSS problems by Anonymous Coward · · Score: 0

      First of all, DavidinAla, you are spamming. Get over yourself. Those who are listening have understood your point. The rest won't. Answering every objection in every thread on this topic is just repetitive and tedious to read.

      Second, for all that you seem to be a graphics professional, you don't seem to understand a fundamental property of CMYK, namely that there is no one right CMYK representation of a given (e.g. Pantone) color. As you note, CMYK is really only needed for printing, and the CMYK representation you should use for a given color is quite heavily influenced by the print process that will be used to render it. As such, in a modern world, images should be kept in a well-defined orthogonal color space (as you do) until ready to print. Then, two bad choices ensue: you can find out from the printer what CMYK conversion will work best with their equipment, or you can try to persuade them to accept a picture in some standard colorspace (e.g. sRGB) and do a good conversion themselves.

      The GIMP should have conversion functions for various kinds of CMYK export. It should also support various standard orthogonal color spaces, and at least 16 bit primaries. However, its inability to maintain a CMYK user interface throughout the edit cycle is a major nuisance, but not a showstopper for anyone who otherwise really wants to use the tool.

    25. Re:Perfect example of OSS problems by Anonymous Coward · · Score: 0

      You realize that tools for converting _as a last step_ from RGB to CMYK Tiff images exists for a while on Linux (and Open Source) ? See Argyll (or LittleCMS ?)

    26. Re:Perfect example of OSS problems by killjoe · · Score: 0, Flamebait

      "I don't think a reasonable person could come to the conclusion that I'm a moron from anything I've written here, so I'll conclude that you have a problem with either reading comprehension or basic logic. David"

      You still haven't told me how you were forced to install and use GIMP.

      As for your moron status other people have pointed exactly how deep your ignorance runs.

      --
      evil is as evil does
    27. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      Ah, so it IS reading comprehension that's your problem. Too bad. I can't help you there.

      David

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

    29. Re:Perfect example of OSS problems by DavidinAla · · Score: 1

      I don't know enough about either of them to comment. All I know is that GIMP by itself isn't ready to be used for what I need. I have actually looked up both of what you mention (because I've seen them referenced elsewhere) and there's nothing about them that makes sense to an end user, insofar as how they'd be useful in getting real work done with GIMP. The things I've been able to find are heavily oriented toward developers, NOT end users, so they're useless to a normal user, as far as I can tell.

      David

    30. Re:Perfect example of OSS problems by killjoe · · Score: 0, Troll

      LOL. So how was it shoved down your throat again?

      --
      evil is as evil does
    31. Re:Perfect example of OSS problems by Crayon+Kid · · Score: 1

      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.

      There is no "OSS" people in the sense you mean here. OSS is a software developing and distribution methodology. You could just as well talk about "OOP people" or "people who use exceptions" taking a stand on desktop development. Sounds silly yet?

      Second, there is no "Linux". There is no central entity with an agenda. There's just loads of geeks doing things for fun and their own use, as you already acknowledged. This will never change. This open development model is a meritocracy: "contribute or shut up."

      The adoption of GNU/Linux in the commercial world and on the users' desktops is mostly a lucky side-effect. The open model simply happens to produce software that is good enough both commercially and from the user POV. There isn't a master plan, there is no agenda, no roadmap, no goals to achieve, no budgets, nothing like that. Not even malice towards end users or artist types.

      Developers are kings. Users come second. Commercial grade quality comes third. No amount of complaining about it will change anything. This is how this thing works. Denying it is breaking it.

      When someone with enough resources is willing to invest time and money and effort into these issues, they improve. When not, they don't. Simple. Some really big open communities have started to do it (Gnome, KDE) as well as some commercial entities (IBM, Ubuntu, Red Hat, Novell, etc.) But don't expect it from the communities at large.

      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    32. Re:Perfect example of OSS problems by dchallender · · Score: 1

      CMYK support (or not) is not that vital an issue.
      My wife does a lot of graphical work as part of her job - posters, postcards, fliers etc.
      She can use photoshop if required..however the printers she most commonly uses do not demand the images in psd format, just plain old jpeg.
      They handle the CMYK aspect of it all - thats the job of printers!
      All my wife needs to do is make sure monitor printer colour calibration side of things is sorted when she does her trial prints before sending it off - so she gets no nasty surprises.
      N.B. She sends them a paper print as well as the .jpeg just so the printers can do a quick "by eye" check after setup and warn her if theres a killer problem.
      Be on good terms with your local printers and using bog standard RGB is a non issue for "everyday" graphics printing (i.e. no weird effects stuff such as metallic etc which does need a different solution).

    33. Re:Perfect example of OSS problems by dbIII · · Score: 1
      but I also doubt that they really see the limitations from the viewpoint of an end user in the print industry.
      To phrase what I said before a bit better - they don't understand the print industry so are talking about gimp being suitable for professional use in other areas. People who do web pages call themselves professionals too (I'm not a web designer - I'm an engineer turned computer wrangler, so I don't understand the print industry either).
    34. Re:Perfect example of OSS problems by Hosiah · · Score: 1
      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.

      Here. What irks me, is that 90% of the complaints about Gimp are complete fallacies. And blowhards like Steven J. Vaughan-Nichols are working against those of us who simply want to educate people. By all means, I would like to see Photoshop ported. Of course, I could care less if people don't like the Gimp. It's a free world; use what you want. But I don't like the mythology that keeps people in the dark.

    35. Re:Perfect example of OSS problems by Hosiah · · Score: 3, Interesting
      You don't have a clue what spamming is, do you?

      Speaking of spamming: for about the 1,000,000th time, Here's the CMYK plug-ins for Gimp. Yeah, one of those non-existant plug-ins the ignorant jackass in the TFA asserts do not exist for Gimp.

    36. Re:Perfect example of OSS problems by just_another_sean · · Score: 1

      ...you just passed with flying colours.

      Pun intended?

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    37. Re:Perfect example of OSS problems by vga_init · · Score: 1
      I get free software that's as good as what I'm using now. If it doesn't, I already have tools that work and a commercial software market that understands how to supply better tools in the future.

      For many of us, the mere fact that a piece of software isn't Free makes it "not good enough." You'd probably call us religious or fanatics, but to me it's a matter of investing in the future. I for one don't believe the market understands how to supply better tools (I grew up with Windows in the home...need I say more?), and it never did supply me with the tools I needed (I couldn't afford professional development software--I learned how to program with pirated MS development tools).

      I still don't believe a lack of features should be taken as an attribution of failure for Free software. Also, it would not surprise me if there doesn't already exist a project (tool or library) appart from GIMP that will do CYMK conversion, waiting to be incorporated. It's very well possible the feature will appear in the near future.

      As for your first comment, you lead me to believe that you just don't "get" what this "missing feature" is.

      I understand what the feature is; I work as a writer for my college's newspaper, and I've had discussions with the photographers and photo editors about it. CMYK is indeed a showstopper, but just for a certain class of people.

      And, yes, the fact that people keep saying that GIMP is perfectly good enough for something -- when I KNOW that it just won't work for this purpose -- tells me a lot about the credibility of the development model.

      It just seems to me that you and "people" have a small disagreement about what that "something" is. I've used GIMP for a lot of different things, including development for a software project, and I've noticed it's perfectly good for a *lot* of somethings. Unfortunately, it's not good for your something.

      Too many of its proponents spew ignorant puffery that would put MS to shame. There are some very good developers doing good work in OSS, but there are way too many people who are willing to pontificate about things they know nothing about.

      Perhaps, but Free software will always be about the folks who are getting the work done and developing the software. There is a large fanbase around that will act foolish at times and pontificate like you said, but my experience is that the main people are wise enough to keep their mouths shut when it comes to things they don't know much about (with the possible exception of Linus Torvalds).

    38. Re:Perfect example of OSS problems by Chanc_Gorkon · · Score: 1

      This definitely is true. I have said it time and time and TIME again....if Linux is to get more users, the developers need to:

      1. Pull thier heads out of thier arses and listen to NON PROGRAMMERS.
      2. When the user makes a REALLY dumb choice (You know that password thingy, I hate having to type it in oh why do I have to do that??), be nice and tell them it would not be a good idea becaus then that creepy guy in Russia can steal thier stuff.
      3. Just because a user asks for something that is hard ir really hard to implement with the code base you already have DOESN'T mean you shouldn't considerate or even completely dismiss it.
      4. Oh and again, listen to the NON-PROGRAMMERS.

      There are tons of people who CAN use computers who are experts at using some apps that can't write the app. That DOES NOT mean thier opinion isn't important.

      Greatfully, I see some projects that are starting to tuen this around a little. Look at iJuice (used to be iPodder) a year ago, Adam Curry would ask for X feature and then others would comment to Adam that it would be a good idea and then bam.....it happens. That doesn't happen on alot of projects.

      --

      Gorkman

    39. Re:Perfect example of OSS problems by gg3po · · Score: 1
      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.

      I do graphic design professionally -- both freelance and fulltime. I once did all the typesetting, etc. for a 600+ page illustrated children's book using nothing more than Gimp, Inkscape, and Scribus. I did all the raster image editing in the Gimp. When it came time to go to press, I just exported to PDF from Scribus (makes excellent press-ready pdf's), which performed a very accurate conversion to CMYK for me. Problem solved.

      --
      ---
    40. Re:Perfect example of OSS problems by gg3po · · Score: 1
      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.

      Or maybe he just uses Scribus to export his finished work to press ready CMYK pdf's, like I do.

      --
      ---
    41. Re:Perfect example of OSS problems by wohlford · · Score: 1

      I'm the Systems Administrator for my company. I used to be the Prepress Manager as well until we hired this fabulous lady to handle it instead. More Slashdot for me. :-) At my company we don't care what color space the image is in. It gets converted to the industry standard SWOP color space (CMYK) no matter if its RGB, LAB, or grayscale by our Kodak Prinergy workflow. Anything that's printed goes through this PDF based system. Its amazing. The software just color converts automatically! :-p Welcome to the new millennium

      And yes, GIMP sucks rocks!

      --
      Jason Wohlford
    42. Re:Perfect example of OSS problems by Tim+Browse · · Score: 1
      he meant "inverse" in the sense that one scheme describes light absorbed and the other describes light emitted.

      That would be true if you were talking about a CMY colour model. Whereas CMYK was the model under discussion, and the very presence of the K component speaks to the real world problems of colour representation, ink saturation, plate registration, etc.

      Seriously, anyone who claims CMYK is just the inverse of RGB can safely be excluded from discussions about colour representation until they learn more about the subject.

      It's a bit like people who complain about their printouts being the wrong colours by saying "But it looks alright on screen!"

    43. Re:Perfect example of OSS problems by Tim+Browse · · Score: 1

      No, actually. I must be getting old :-)

    44. Re:Perfect example of OSS problems by spitzak · · Score: 1

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

      Actually that is wrong, what you are describing is what Gimp does, or what printer drivers do when transferring an RGB input to a CMYK output.

      What is missing is to actually store and paint the 4 values for CMYK. Mathematically you cannot convert these 4 values to 3 and recover the original 4, thus any image editor that stores RGB cannot reproduce all possible CMYK settings. Photoshop does this and Gimp does not.

      Everything else discussed such as color management or pantone, etc, is missing the real problem. You can argue that there is no need for more than a 3-dimensional space of colors and that a very careful and well-defined conversion to CMYK will be sufficient. That is a reasonable argument, but it is not what the Photoshop users claim.

  46. 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
    1. Re:Underrated point by Gordo_1 · · Score: 1
      GIMP will never have more than a marginal user base because they don't understand their users.

      ...and furthermore, GIMP developers aren't incented enough to care. That's why in a company driven by profits, you hire Product Managers whose primary job is to ensure that user needs are addressed. If the GIMP had a company with a real vested interest in creating a viable Photoshop alternative -- say, like Red Hat is to Linux -- then you might see some positive developments.

    2. Re:Underrated point by Anonymous Coward · · Score: 0
      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.

      Yeah, and what would you do with a moon on a stick, and where would you put it, anyway?
    3. Re:Underrated point by cortana · · Score: 2, Interesting

      So I guess Apple should give up OS X and just rip off the interface of Windows? Should Microsoft ditch their attempt to revolutionise the interface of Office 12?

      Face it, the reason Apple and MS can get away with non-conformant interfaces is because they spend a lot more money on marketing.

    4. Re:Underrated point by Hosiah · · Score: 1
      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.

      This argument is the one I have a hard time wrapping my brain around. Tell me, why aren't toilets shaped more like diapers, since 100% of the users learning toilets graduated from diapers and are expecting the same interface? How did cars ever catch on, since 100% of users new to cars had grown up with horses and buggies and expected the same user interface. How do you suppose people getting trained to fly Stealth Bombers can ever manage, when the interface is so different from the cars they've been driving?

    5. Re:Underrated point by MtViewGuy · · Score: 1

      Another huge advantage of Photoshop is the fact a LOT of third-party add-on programs exist for Photoshop, something that GIMP seriously lacks.

    6. Re:Underrated point by 99BottlesOfBeerInMyF · · Score: 1

      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.

      I'm going to have to add my voice to those disagreeing with you. I'm a regular photoshop user, an occasional gimp user, and I've spent a lot of time studying UI design. The fact of the matter is, while having a UI that is very similar to photoshop makes it more learnable to switchers, it is neither a good long-term strategy, nor all that important. Photoshop's UI is pretty average. It is usable, but has plenty of failings and I often find myself wishing that the UI was not in my way for some trivial task. It is also only middle of the road for learn-ability. I've instructed a number of others in using image editors and photoshop is just not very intuitive.

      Gimp, on the other hand, is abysmal in both categories. It breaks UI conventions left and right and took me a long time to learn. Instructing others in its use turns into a commiseration over how bad the UI is. The designers obviously don't have any budget to do a proper usability study and it shows. They also do not seem to have even tried a half-assed usability study with their friends and relatives.

      Gimp is a project not a product and this is both a good thing and a bad thing. It is free and it is customizable, but unless it gets some real backing I don't see it as any threat to photoshop's market.

      One thing I'd like to mention. Right now is the best time to put a big dent in photoshop's market. I don't expect we'll see photoshop running smoothly on OS X-Intel machines for well over a year. Photoshop is a slow dinosaur, especially on OS X (the platform of choice for most graphics professionals). Their code is old, and does not take advantage of the features of OS X for reasons of maintaining the same feature set on a certain outdated OS. Right now is the time for a competitor to grab a big chunk of the market with an innovative new graphics program that does what most users want, but better and faster and cheaper.

      For those of you who are as disappointed with the gimp as I am, try looking at krita on Linux. It may be more what you are looking for once it matures a little.

    7. Re:Underrated point by Alpha_Traveller · · Score: 1

      I have to agree with this wholeheartedly. UI is everything in the world of Photoshop. It's why their lawyers protect the UI carefully. It's also why every change to the UI in Photoshop is tested and retested and agonized over and the team working on it is locked in a closet and only allowed to come out for NAPP meetings when there's a new feature to show off.

      If the GIMP community wants to compete then they must get people on the project who have total control over fashioning the UI. In fact they could do something the Photoshop team won't DARE do, which is create several different UIs for GIMP, or allow people to completely reconfigure the shape of the pallets, the buttons, etc. That way if the user wishes to make it look like Photoshop they arrange it to do that themselves, thereby keeping the lawyers from whining about how GIMP stole PS's UI. It's not GIMP that does it you see, it's the USERS to who do that.

      Or, alternatively a user can configure an interface with their favorite settings, in the order they wish them in.

      Sure it's configuration hell, but it's time the GIMP team give up their current lousy UI. It has been years, and face it --- your potential community knows more than they GIMP UI team knows. They know it doesn't work for them, and THAT's why they stay away.

      --
      "Love is like pi - natural, irrational, and very important." (Lisa Hoffman)
  47. gimp is great by asv108 · · Score: 1
    For a lot of web work and casual image editing, but its not up to snuff for any professional print or photography work. Whenever a casual user wants to do some quick image editing, I always recommend gimp, but I certainly wouldn't recommend Gimp for somone who does editing for a living.

    Does gimp have any major corporate backers? I think part of the problem is that open source developers tend to scratch an itch, i.e. solve a problem that they want to solve, not write code for a feature that they have no intention of using. The interface could also use a major reworking. It should really be written with photoshop users in mind.

    I know people like to do their own thing, and oh how much did the earily open source desktop enviroments get blasted for looking like windows, but Photoshop has over a 90% market share. If gimp is to become a serious photoshop alternative, it would need usable by photoshop users right off the bat, without retraining or documentation.

  48. Good docs are another Photoshop advantage by Sycraft-fu · · Score: 2, Insightful

    Adobe offers these kits called Classroom in a Book and they are wonderful. Geeks might actually not like them, but they speak the language that artsy types understand. My mom had great success with a Photoshop class, and she says that is one of the biggest reasons. She's not a computer person, she finds them difficult to learn and needs precise instructions, with visuals preferably. These books provide that and using them, she's now gotten far better at Photoshop than I am.

    This is extremely important, given that non-computer people are a major market for Photoshop and such. Sure geeks need to use photo editors, but let's be real here, we aren't the core market. The art people, be they prepress, photographers, designers, whatever, they are the ones that really make use of these products. However their computer skills are generally minimal, limited only to knowing what they need to work their tools. Thus having good training material is essential.

  49. GIMP, Flexibility and Usability vs Photoshop by betasam · · Score: 1

    The Gimpshop page clearly shows that most people seem to want a familiar interface when having used photoshop earlier. The other reason maybe the host of available plugins to photoshop (Kai's powertools and a few others that they already own) for the digital image manipulation business. But as Gimpshop clearly shows, Gimp can be hacked and made to look like photoshop for the average photoshop user. I am not sure this is possible with Adobe's photoshop itself. So Opensource and its flexibility from which GIMP is born far outweighs photoshop. IMO, GIMP is already better than photoshop thanks to flexibility. For those who haven't been able to hack it themselves, they just need to ask a group of hackers to help them with a Photoshop look and feel, compatibility with photoshop plugins if they are already used to the other application. No need to look for Photoshop killers here, Photoshop has been in use (like MS Windows) and has been quite a well written product. The GIMP has reached a far more flexible state matching features in a shorter period of time due to a large user base. With a few more hacks, usability, look and feel options and plugin support for third party plugins, for the GIMP it is only a matter of time before Adobe will need to rethink their Photoshop strategy.

    --
    No Greater Friend, No Greater Enemy! (Lucius Cornelius Sulla)
  50. crop by br00tus · · Score: 2, Insightful

    I am a normal user and not a graphic designer. Thus, I do not use complicated features in Photoshop or GIMP, just the low level features. One of these, however, is crop. And crop sucks on GIMP. With Photoshop it is simple, I put a box around what I want to crop to and I crop. With GIMP there are three crops, none of which are very good. The only one that I can use is "guillotine", which one uses by going to the ruler, dragging a line out to the middle, going back to the ruler, dragging a line to the middle, going to the other ruler, dragging a line to the middle, going to the other ruler, and dragging a line to the middle again. Then I go through the menu to guillotine crop, and 9 images pop up. I close the eight I don't want, so that I now have the original big one, which I don't want any more, and the cropped version. I can just imagine what the more complex features are like. Or what people who aren't like me think, who don't use Debian as their desktop.

    1. Re:crop by kbmccarty · · Score: 1

      I am a normal user and not a graphic designer. Thus, I do not use complicated features in Photoshop or GIMP, just the low level features. One of these, however, is crop. And crop sucks on GIMP. With Photoshop it is simple, I put a box around what I want to crop to and I crop.

      I'm no graphic designer either, so maybe I misunderstand what you mean, but you can do exactly that in GIMP. (I'm not trying to defend GIMP's shortcomings, but I don't think it deserves this particular criticism.) Using the select tool, create a rectangular selection in the image. Then, right-click on the image to get the context menu, and select "Image->Crop Image". Am I missing something here?

      --
      - Kevin B. McCarty
    2. Re:crop by 00lmz · · Score: 1

      I don't think it's that hard. In fact, I had to work to find the Guillotine command in the menu. On my Debian (sarge) system with GIMP 2.2.6 I just select the area I want and select Image > Crop Image from the menu.

      The so-called "crop or resize" tool is another story altogether. I tried to use it and just after I started to hold the left mouse button down on the image, a dialog box popped up showing the options for the tool, right on top of my image. Not being able to see the cursor when you're holding a crop tool that you are afraid to let go isn't very comforting :) .

    3. Re:crop by Canordis · · Score: 1

      Which version are you using? On 2.2, which isn't even the newest version, you crop by clicking on the crop button, dragging a square on the image, and clicking on the crop button on the crop dialog that pops up. The dialog is there to let you fine tune the cropping to a specific size, if you need to, along with a couple of other features.

      --
      I have never made but one prayer to God, a very short one: "O Lord, make my enemies ridiculous." And God granted it.
  51. Instead of getting upset, why not get better? by NorbrookC · · Score: 1

    This was what Novell was doing in their survey:

    Novell, through its CoolSolutions community-relations website, is conducting an online public survey to determine which Windows-only applications are most likely to keep Windows users from migrating to Linux. The company also wants to know which Windows-only apps would be most popular on Linux desktops if they were ported to Linux.

    IOW, what keeps a Windows user from migrating, and what do they want to see ported the most? Irregardless of the Open Source versus Closed source battle, the fact is that most of these applications have been around longer than Linux, and have survived this long because they offer better features and ease of use. Right now, that isn't always the case for the Linux apps. It's getting a lot better, but it's uneven.

    It's the same problem faced by many different groups. Yes, we'd like to switch, and yes, we can see the benefits. But, the applications we need are either not there, crude, or require programming skills to get them to work.

    I'm currently working with a group that would love to start bringing Linux into their industry. Unfortunately, half the applications they need simply don't exist, and no one is even beginning to develop them. There are half-a-dozen or more different programs in Windows and Mac for each of the application functions they need, but not in Linux. Like it or not, and they don't, they're stuck.

    Rather than getting defensive, and attacking the messenger, why don't we take it as a challenge? OK, they want this. Our current application sets for that purpose aren't up to their demands, so how do we get better and make it meet their demands? That's what will push Linux, not telling people they're stupid and ignorant for not rushing in!

  52. Software patents by Schraegstrichpunkt · · Score: 2, Insightful

    IIRC, the GIMP is lacking a lot of things because of software patents.

    1. Re:Software patents by BigSven · · Score: 3, Informative

      Actually no. The main reasoon GIMP is lacking lots of things is lack of active developers. There's really nothing that keeps us from adding support for high color depths and/or other color spaces like CMYK except that GIMP is being developed by a small group of volunteers with limited free time. If you want to help out, there are plenty of tasks in our bug tracker over at bugzilla.gnome.org that are waiting to be implemented. The GIMP developers will be happy to hold your hand and answer your questions.

  53. No recent filters by GrouchoMarx · · Score: 1

    My issue with The GIMP is that anytime someone sends me a Photoshop file that uses a filter that was added to Photoshop after around version 6, GIMP ignores it. More often than not, that makes the image look like ass.

    Photoshop is currently on version 9 or so.

    It's the same issue as .Doc compatibility for OpenOffice, but GIMP's support is WAY behind. I simply can't work with, or create, a reasonably interesting (by even 2004 standards) composite graphic using The GIMP. I could if I had Photoshop, and everyone I work with that uses Photoshop does often. That's the biggest problem for me.

    --

    --GrouchoMarx
    Card-carrying member of the EFF, FSF, and ACLU. Are you?

  54. They just do different things... by Urza9814 · · Score: 0

    I gotta say, I've used both Gimp and Photoshop, and I actually much prefer Gimp. It seems to me that, while Photoshop has a lot more options for enhanching photos, it doesn't come CLOSE to Gimp for making an image from scratch. Between the masses of Script-Fu and the large amounts of Filters, Gimp's got that covered. I was playing with Photoshop at school the other day, looking for a render lava, or perhaps circuit board, and found that it seems to only have variation of cloud! I mean, it might be nice for refinishing those old pics you found in the attic, but you can't get any cool pictures straight from Photoshop...
    And I gotta say, I HATE Photoshop's interface...I HATE it! The Gimp's just seems so much smoother and nicer...I spent, like, 10 minutes looking for a bucket fill on Photoshop, only to just give up and use a brush...And when you select something you have to manually go into the move selection thing...I dunno, I just like Gimp's interface...it's a lot smaller and easier to work with. I don't want all those buttons, I don't NEED all those buttons, and there's absolutely no reason to have the friggin' thing take up the whole screen when I'm only working with a 50x50 image or something. Gimp only takes the space you need...so your AIM and Winamp and whatever isn't blocked out by this massive bloated ugly-ass program window.

  55. Power is as power does by jd · · Score: 1
    GIMP is powerful - I use it a fair amount - but if people are finding it can't do what they want, then it's not powerful enough in the right ways.


    One thing I don't like about any existing drawing/CAD package is that virtually everything out there assumes there's only one kind of user in the world only interested in doing one kind of task. (Or very close to that.)


    I guess I've become spoiled with the flexibility of Slashboxes - I like being able to pick and choose the sorts of things that are visible, not being stuck with just one or two views. I guess I also run into the limitations of programs a lot - which either means the programs aren't flexible enough, or I'm just too weird for the coders.


    Photoshop is standard. Fair enough. But if the menus and key sequences are soft-coded, you can write a skin to reproduce Photoshop's user interface. The same goes for Corel Draw, FontLab Studio, etc. Ultimately, you're manipulating some combination of bitmaps and vector diagrams, with some sort of mechanism for grouping and attaching components, plus a bunch of absolutely bog-standard scripts for defining lines, curves and outlines.


    (You wouldn't WANT all of those capabilities in one program, but if the framework is solid and the scripting is powerful, you could plug in whatever combination you wanted with whatever interface you liked.)


    People have been able to write modular code to some degree for at least the last 25 years. Computers and Operating Systems have had the power to sport highly sophisticated engines for almost as long. I fully understand that we need specific programs ported to this, that and the other, I just don't see why there's so little sign of moving past that point.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  56. Difference of two softwares' in the makings by layer3switch · · Score: 2, Insightful

    IMHO, Photoshop is made for and by graphic designer while GIMP is made for and by programmer.

    Besides, if GIMP project had half of financial backing as Adobe Photoshop, it could be different picture. I think, it's helpful to take this as a constructive criticism and not as spreading salt on bleeding wound.

    --
    "Don't let fools fool you. They are the clever ones."
  57. Even the most basic function is weird with Gimp by Anonymous Coward · · Score: 0

    I downloaded it the other day, all I wanted to do was a crop. I just had reinstalled my comp and I felt downloading Photoshop was wrong especially since there is an open source alternative. I use Open Office and I like it pretty much so I assumed a software that is as popular as Open Office should be at least decent. After 10min. of using it I still couldn't crop my picture, I found a crop menu into which I had to input which part of the picture I wanted to crop numerically (!!??) but I couldn't find a simple tool that would make me select part of the picture and crop it.

    Before you go on on how stupid one must be because you actually know how to crop keep in mind that no simple task seemed weird to perform in Photoshop, not even back when I was using version 3.x for the first time, one of the first software I used on a computer. Stuff like select, crop, draw, fill color were pretty intuitive, select the tool and use your mouse to activate it in the most logical way there is. If Gimp can't let me crop, just crop, without me having to search how to, it fails, period. I didn't went any further, it was useless, I downloaded photoshop.

  58. GIMP vs Photoshop by JWSmythe · · Score: 1


        I see the biggest reason for people wanting to use Photoshop instead of GIMP is that people are comfortable with Photoshop.

        I used Photoshop for a long time. When I started switching over to Linux as my primary OS (two machines on my desk, one Windows, one Linux), I had problems figuring out GIMP. It took me a while.

        Now, I'm great with GIMP. I do things with it, that most Photoshop users can't figure out. As far as I'm concerned, and for what most people do, they're interchangable. BUT, for a user who is only familiar with Photoshop, and uses it daily for work, it's impractical to tell them "Ok, learn GIMP now."

        I no longer use Photoshop for my own work, but I do help people with Photoshop on theirs.

        Some people are "stuck" with their choice in software. I don't consider Photoshop a real problem, it's a great piece of software. I'd love to see it available for Linux, then I'd have another great choice in what to use on my Linux workstations.

    --
    Serious? Seriousness is well above my pay grade.
  59. It's not just usability by Anonymous Coward · · Score: 0

    If you are total novice user of Photoshop, GIMP appears to do exactly the same thing. It can produce the same flaming-text logos, the same lens-flare rollovers, and the same simulated-pencil photo filters.

    If you are a middling-to-professional user of Photoshop, they aren't even in the same class of application - the functionality is fundamentally different.

    Two applications can have the same exact feature list, but utterly different functionalities. This is certainly the case here.

    So the problem may be that the programmers of GIMP are not expert imaging software users.

  60. One word... by stubear · · Score: 1

    ...integration. Photoshop works well with InDesign, Illustrator, Premiere, After Effects, EncoreDVD, GoLive and soon it will have flawless compatibility Dreamweaver and Flash/LiveMotion. While laying out a document in InDesign I can easily click on teh PSD documetn linked to my page and edit the file in Photoshop, save the changes, and have those changes updated in InDesign. AfterEffects works the same way. In both LiveMotion and EncoreDVD I can use Photoshop to create the base artowrk to add visual effects and inteactivity to, all the while alowing me to easily and conveniently link back the original Photoshop. Premiere picks up on alpha channels embedded in the PSD file (as do AfterEffects and InDesign) making it easy to create masks for layering elements in these apps. It is insanely easy to jump between these apps and be creative without the UI getting in the way.

  61. That is what happens by SensitiveMale · · Score: 1

    when engineers design the interface.

  62. gimp won't do. why? No CMYK. by Ralph+Spoilsport · · Score: 1
    it's really very simple - if I can't work in CMYK colourspace for professional colour separation, then the app is a nonstarter - it's dead right out of the gate.

    when gimp can do CMYK, I'll look at it. But until then - sorry - I have work to do, and I don't get paid to futz around with stuff that doesn't work - I get paid to Make Shit Happen, and if it is in print, it's in CMYK, period - no ifs, no ands or buts.

    RS

    --
    Shoes for Industry. Shoes for the Dead.
    1. Re:gimp won't do. why? No CMYK. by slim · · Score: 1

      it's really very simple - if I can't work in CMYK colourspace for professional colour separation, then the app is a nonstarter - it's dead right out of the gate.

      In understand this, but the survey in question was of general computer users, not just professional designers targetting print.

      Do that many people /really/ design for professional print media?

      My perception (read: "guess") is that *most* Photoshop users use it to tweak JPEGs. They do not require colour accuracy within great tolerances and probably don't have the hardware to do that anyway.

      Such people will have invested some time learning to do what they want to do in Photoshop. The GIMP can probably do what they want, but they'll be put off by the learning curve and by FUD.

  63. Printing Problems by slateX · · Score: 1

    I have found that the printing functionality of GIMP is pretty sub-par. I had to print a picture and center it on a page. I could not find any centering options in the print options in gimp, so I expanded the image to be as large as the printable area on a piece of paper, and manually centered the content. When I printed that, the white space was ignored and my image was printed in the corner of the paper. Great.

  64. i agree by digitallysick · · Score: 0

    Gimp is a great app, and considering its free, its great, but it doesnt touch photoshop at all. Photoshop is easy for novices, as well as experts

    1. Re:i agree by fishbowl · · Score: 1

      I use Photoshop CS for manipulating my images, which usually involves perspective compensation and color correction. But I use GIMP for editing icons and UI elements! I prefer each of these programs in different situations and I would not want to do without either of them.

      Also, I routinely run PS under a Win2000 VMWare machine, but I don't print that way, because I have to use native printer drivers to get proper ink control.

      I'm an amateur photographer but I have an 8MP camera and I like to make large prints. I pay a lot of attention to color, and this is not an area where GIMP really competes.

      It's not the GIMP developers' fault, for the most part. Many of the desirable features tread into IP-encumbered implementation territory. There's no way you can even work with standard colorspaces because there are arbitrary barriers to entry in that marketplace, but there are lots of other issues that even a mildy serious photographer will run into quickly.

      But like I said, there are things that are easy to do in GIMP that would be a chore to do in PS. It really isn't a choice that I would make between these two programs.

      The way I see it, everybody already has GIMP, take it or leave it. That leaves the only question: Do I need Photoshop? The answer might be, you only need Photoshop Elements, which can often be obtained free-as-in-beer anyway (bundled with cameras, and with certain books).

      Or maybe you can get by just fine with GIMP. It does have some excellent features and for certain kinds of tasks, its usability is better than PS.

      --
      -fb Everything not expressly forbidden is now mandatory.
  65. Story as troll? by gothicpoet · · Score: 1

    Who are we kidding? This was like throwing raw meat into a lion's den. Linux fan boys will rally to Gimp, and graphic designers will rally to Photoshop. Truthfully I haven't tried to use Gimp in a while but the last time I did I was very unimpressed. But that's just my experience. Just posting this story to Slashdot should get a Troll mod!

    --
    Quoth he ::
    "It's all academic anyway..."
  66. How much is enough? by FishandChips · · Score: 1

    Why should the GIMP or any other program be "enough for Linux users"? If Linux users don't think a program is up to snuff, they've a perfect right to say so. Linux is not a soup kitchen.

    Every time the subject of GIMP vs Photoshop comes up (which is too often), it ends in a flamefest. All one can say is that the market seems to have voted solidly for Photoshop, but many of the voters may well be individual users who won't ever need Photoshop's wider ecosystem of plugins and who won't ever pony up several hundred bucks for Photoshop anyway. Wishful thinking, perhaps?

    For me, the key passage in the article is this: "Photoshop really is a platform, not just an application. When you're buying into an entire system, as the graphics business clearly has, the upfront cost of a single application doesn't amount to a hill of beans in the buying decision." The same applies to dtp of the Quark/InDesign kind and no doubt plenty of other things. Porting a single program to Linux won't on its own bring in the pros, I guess, and you can't port an ecosystem come platform. That needs a real commitment and organic growth over many years. Way to go.

    --
    Las qué passoun
    tournoun pas maï
  67. Classic geek denial by Xonstein · · Score: 3, Insightful

    There are just too many Linux people who feel that because you can accomplish this task or that with an application that it is somehow 'just as good' as another application. They refuse to accept the fact that the Human Interface Design, professional documentation, and seemingly 'minor' features the Linux application lacks are User interface, designed workflow control, and substantially deep and broad documentation options and third-party support are HUGE, not marginal, elements of an application like Photoshop. ITS NOT JUST A BUNCH OF FILTERS. Also, most if not all GIMP features *follow*, not *lead*, photoshop implementations. Like most Linux desktop applications, it seeks to duplicate the features and usability of the gold standard commercial app, not lead it. Someone else mentioned that you dont need Dreamweaver to develop webpages - entirely true - but if you are a professional website designer 90% of your workflow revolves around constant mockup revision negotiation between client and designer, following by a final code implementation. Using Photoshop and/or Dreamweaver to revise mockups moves MUCH faster than hand-coding, and as such saves time and money. Also, it is advantageous to design in PS and/or DW because you focus on what the final page needs to look like, and not worry about how it needs to be coded, which is huge.

  68. My opinion on the main reason by bm_luethke · · Score: 2, Interesting

    They give quite a few points to consider, and I'm sure they all factor in. But most of them are just "I don't want to change" - while that is a valid idea (for a busness you need to justify the cost in retraining - just doing it for political reasons rarely works), but cost may eventaully be a factor. Especially if Photoshop tends to become the only platform stopping the migration.

    However, those are just essentially icing on the cake with the other main problem (and I focus on it more because it's a universal problem):

    "Another problem, according to my buddies, is that besides Photoshop itself, there are hundreds of Photoshop plug-in programs. Of those, everyone has their handful of favorites that they use on most of their projects. GIMP simply doesn't have anything close to this sort of third-party add-on software community."

    With something like that, it's not a "I do not want too" but a "I can not". The 8bit problem would be in the same class.

    There are many GPL software platforms out there that compete well in functionality with their commercial counterparts. I know my parents would love switching to Linux if they could (based on cost) but even if there is a comparable program to Autocad there isn't a land surveying plugin comparable to Eaglepoint and most likely never will be (unless Autocad is ever ported to Linux and enough land surveyors switch). It's not a matter of want or ease of use - they can not get thier work done under Linux.

    There is something of wondering why the smaller companies will not port, after all many of them support different Unix variants. Ultimatly when I've asked with the few tertiary software producers I use it's generally the same problem - the political end of Linux is a big turnoff.

    It's something I've felt strongly about for quite a while (but can't make up my mind which path to follow). Linux - and it's community of people and projects - is at or nearing a point where it is going to have to decide if they want to be commercial or play second fiddle. Rightly or wrongly, too many people are turned off by the strong political movement. Commercial software is not going to be political - that eats into profits. Even the companies like IBM that have been pretty strong in OpenSource work tend to use it because it benefits thier bottom line. People may want both, and some people may be happy with both, but the general business community is not going to accept it (again, rightly or wrongly it doesn't matter - there are times I don't like gravity and wish it were not so but it doesn't change anything).

    I'm not saying the political end is bad or inferior (this particular post is biased towards commercial acceptance because of the parent article) - I really like the GPL and the OpenSource philosophy. If that is the direction the community chooses fine by me, I like it. But I don't think it's possible to do both, too many smaller companies that can not make money from service - only from selling - are not going to embrace Linux. Yes I know they do not have too, but the community is still bent towards it to the point that most are not going to enter into it - can you imagine if ALS or OLS were flooded with smaller companies selling software (such as major Windows conferences are)? It's what is going to have to happen for general Linux acceptance (either it happens first, as a consequence of acceptance, or conferences like ALS and OLS become small irrelevant conferances and the ones that embrace it are the big ones - thus you must choose one over the other). Not to mention smaller companies noticing how the community reacts to places like Nvidia giving binary only drivers (again, if you want to focus on the political espects perfectly fine, if you want general commercial acceptance it really hurts to do it). It's not the big companies blocking it - they go where the money is and have plenty of money to shift if they need too, it's the myriad small, specialised, and essential tools that are stopping it. There is little talk or focus on these types of applications but they probably make up a larger percentage of make or break software for many companies.

    --
    ------- Sorry about the spelling, I suffer from two problems. Dyslexia makes it difficult to spell well, lazy makes it
  69. Here's why by Anonymous Coward · · Score: 0

    I'll reply to you. Here's the reasons why I prefer to use Photoshop, ordered by importance:

    1. Where are my blending options? I want to be able to bevel, emboss, texture, etc. on each layer with an easy to use dialog. I don't want to fiddle with 5 layers, each filtered their own way just to achieve a button. And I want immediate feedback.

    2. The GIMP's GUI has gone down hill and there's no sign of returning. The selection tool has been screwed up since I can remember (shift to add AND to make regular shapes like squares), and then they screwed up the file dialogs by listening to Gnome.

    3. And yes, color support. I've only been able to achieve some effects with CMYK.

    It has nothing to do with learning time. It's all about usage time and design. Photoshop clearly wins because Adobe has listened to their customers. The developers of the GIMP have not.

    1. Re:Here's why by typical · · Score: 1

      1. Where are my blending options? I want to be able to bevel, emboss, texture, etc. on each layer with an easy to use dialog. I don't want to fiddle with 5 layers, each filtered their own way just to achieve a button. And I want immediate feedback.

      Granted, not there today, but if my understanding of the gegl rework is correct, it should be easy to feed a layer into a "series of operations", and when updating that layer, have the "series of operations" reapplied. Basically, if you can store a directed acyclic graph of operations to be applied, it becomes a trivial operation to make a layer an "effect layer".

      3. And yes, color support. I've only been able to achieve some effects with CMYK.

      Also will be in gegl.

      --
      Any program relying on (nontrivial) preemptive multithreading will be buggy.
  70. apps by paintbrush12 · · Score: 1

    I would like to remind you of LINUX leap into holly wood and how MANY of the newer breed of Visual Effects artist . need new tools i for one use MAYA, Houdini and SHAKE on a linux platform and a good stable port of phototshop would do wonders when i need to texture something remeber not all of us are programers first . i'm a visual artist first and programer when i need to be . i cna peck out code .but dreamweaver would be a nice port for doing Daily pages . for production . i've been asking adobe for 3 years now WHEN??? becuse i do OWN my licenses . i'd also like to see a few other things . for one google Earth .. shame on you google for not porting that yet .. it's to much fun... but that is my 2 cents ,from an Artists perspective .if we had a few more tools i'm fairly certain i'd beable ot move my last 2 pecies of software over and be done with ti . right now i need mainly photoshop, then the rest of th eadobe editing line .. aftereffects i can do without as long as i have SHAKE, which by the way works better on a LINUX platform then it does in it's native MAC OS ..sad actully considering ther cousins . i'd like ot see AVID/ AVID exspress on linux .again a cousin as it already runs on BSD based OSX... also protools . industry stadard things make life easier. another reason VSFX artist ,would benifit is a LOT of our software we use now .(SHAKE and HOUDINI inperticualar) use UNIX file structure, and will intigrate easily with tereminal . it's asier batch rendering from terminal , when you don't want to waste percious system resources .. but i degress. give me photoshop so i can burry my windows box . i need ot free up some harddrive. i found a good emulator for the few games i play so give me photoshop so i can dump M$. /rant Mary- Hill VSFX student at SCAD.

    1. Re:apps by Achromatic1978 · · Score: 1

      Please tell me as a graphic designer, you have your copy proofread after you get your hands on it. Speaking as someone who has an office with several Avid DS Nitris suites set up, what exactly would you gain by having Avid run on Linux?

  71. Photoshop is a Killer App by miyako · · Score: 2, Informative

    I use Linux as my primary desktop OS. I have to say that I agree that Photoshop would definitely be a huge boon to be able to run on my desktop. Right now I have a mac that I use for photoshop and although I really like it, it would be very nice to be able to not have to get up and move to a different machine to be able to mess with some textures. While GIMP works for some things (and it actually feels faster working with some larger files than photoshop on similar machines)- the lack of certain plugins (generating normal and image maps, working with .iff files, nVidias photoshop plugins) means that gimp isn't exactly practical.

    --
    Famous Last Words: "hmm...wikipedia says it's edible"
  72. Why _should_ I use The GIMP? by vijayiyer · · Score: 2, Interesting

    Let's see: as a photographer, the GIMP is missing 16 bit support (showstopper), the healing brush (saves me hours of time doing dust removal and the like), adjustment layers, speed (I work with 300-500MB large format scans), proper color management, etc. Someone tell me - why _should_ I use The GIMP? To save a few hundred dollars - a small fraction of my total equipment cost? Being the dominant player, it's not for Photoshop to justify its existence - the GIMP needs to provide a compelling reason for people to use it, and I see absolutely none for serious users.

    1. Re:Why _should_ I use The GIMP? by Ford+Prefect · · Score: 1

      Let's see: as a web programmer, the Commodore 64 is missing 32-bit support (showstopper), speed, memory (I work with source code reaching several hundred kilobytes), a proper colour display, etc. Someone tell me - why _should_ I use the Commodore 64? To save a few hundred dollars - a small fraction of my total software cost? Etc. Etc. Etc.

      ...

      If you need Photoshop, then go ahead and continue using it. Whinge to Adobe if it doesn't work on Linux, not free software developers. The GIMP's fun, free, written by hobbyists and for certain tasks is quite capable - for people like myself, who like mucking about with building new computer game textures, create simple graphics for web development and occasionally fiddle with photos we've taken, it's great. And slightly cheaper than Photoshop. ;-)

      After around eight years of using The GIMP, I've found I can sit down in front of Photoshop and often, within minutes, be far more proficient in its use than the official user of that computer. Have I thought about buying a copy? Yes - but right now it doesn't really offer me anything that I can do in The GIMP already. That may change - and when it does, I'll buy a copy of Photoshop. It's bloody awesome software, after all - but for the moment, I'm quite happy with my metaphorical little Commodore 64...

      --
      Tedious Bloggy Stuff - hooray?
  73. Colour depth. by sbaker · · Score: 4, Informative

    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
    1. Re:Colour depth. by Anonymous Coward · · Score: 5, Interesting

      The mailing lists don't just have the developers biting at each other, but some of the higher up gimp people biting at users and potential users. I dared to compare a feature of Photoshop's clone tool with one on GIMP, and wished for some of the photoshop-like functionality on the gimp, and gimp's resident defender Carol started on with the nasty emails. It was six repetitive emails abusing me, my relationships with women, abusing me for being a control freak and how, by insisting gimp wasn't good enough, I was calling all gimp users morons for using substandard software and she wouldn't stand for that. That's borderline stalking behaviour.

      What happened 3 months later? My graphic designer gf got exactly the same treatment in email off list for asking how to do something in gimp that she could do in photoshop, except carol added in the accusation that she could only afford photoshop if she's sleeping with the boss so she didn't have time to speak to people like her. That didn't stop her sending another couple of abusive emails.

      This is an open source software mailing list, not a vicious political shitfight where nobody's allowed to question or suggest the slightest thing is wrong with Gimp. Works more like the latter from my experience.

    2. Re:Colour depth. by tcdk · · Score: 2, Interesting
      The problem is at the core of the GIMP developer team's culture.

      I think this is the problem of quite a few OSS projects. We wanted to give our users (of a closed source system) an extra database alternative and decided to take a look at Postgresql, as it doesn't get much more free that that (with MySQL not being that free anymore).

      Reading through some of the postgres mailing liste, trying to find a bit of information on how to do some fairly basic stuff (something like the mysql command "show databases" to get a list of databases), didn't turn up much, except people being flamed then they tried to suggest something.

      I did finally figure it out (do a select on a system table with a few conditions), and decided to add the information, in a note, to the online postgresql documentation. Only to have it deleted!

      We dropped postgresql shortly after (before releasing it), as there was simply to much of our sql that had to be rewritten (sql that worked fine with both mysql and DBISam).

      --
      TC - My Photos..
    3. Re:Colour depth. by BigSven · · Score: 3, Interesting

      Carol is not representative for the GIMP developers. The last time we heard about her sending such mails off-list, we asked her to stop it and were told that it wouldn't happen again. If it did indeed happen again (as you said), I would like you to report this incident and show evidence for it (but please not here on slashdot). If your claims are true, then it is probably about time that Carol gets her gimp.org mail address and web space revoked. We have been hesitant to do that until now because she is often very helpful and the content of carol.gimp.org is a very good resource for GIMP users. But her attitude towards some people on the mailing-list is indeed inacceptable and I am afraid that she is doing more harm than good.

    4. Re:Colour depth. by Forbman · · Score: 1

      Yes, PostGres SQL is much closer to standard ANSI-92 SQL than is MySQL SQL...

    5. Re:Colour depth. by Anonymous Coward · · Score: 0

      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.

      Amen! After a few abortive attempts to get involved with the GIMP project I refuse to go near them again. Hopefully krita will be a better FOSS project.

    6. Re:Colour depth. by Anonymous Coward · · Score: 2, Interesting

      She has sent dozens if not hundreds away in anger (or possibly crying) and you are just now realizing that?

      I mean, the Gimp mailing list is among the unfriendliest places there is on the internet, but come on. This is hardly news.

    7. Re:Colour depth. by BigSven · · Score: 3, Interesting

      We have realized this a long time ago and have discussed it several times. But a mailing-list is a public place. You don't throw someone out of a public place just because you don't like him/her. Especially not if he/she is also often being helpful and he/she is one of the few people who are actually contributing to the project. It is a difficult situation but at some point it needs to be dealt with. That's why I was asking for evidence so that we can bring it up again if needed.

    8. Re:Colour depth. by __aaltii7299 · · Score: 1

      Maybe it's time for a serious fork from GIMP that embraces CinePaint and FilmGimp and is a lot less unixy. From what I've seen Gimp's usability has festered for over six years under a team that ignores user requests, if it was possible to take it away from the current development team I'd say do so. Otherwise move to Krita it has an interface that works, as for content just give it time. I've already started using it in tandem with Inkscape for very basic stuff because it's comfortable to use.

    9. Re:Colour depth. by __aamkky7574 · · Score: 1

      You don't appear to be the only one who's had, um, problems with her:

      http://blogs.gnome.org/view/bolsh/2005/08/30/0

      http://www.martianrock.com/?p=130#comment-1676

      I sympathise; I've noticed - and it's just a generalisation - that open-source application forums/mailing lists tend to be minefields compared to industries one. I've posted countless, sometimes dumb questions about Microsoft Word on various groups over the last 13 years, and didn't once get a snippy remark. Having recently moved to DocBook, my experience with the forum for one particular associated application has been chastening; to say I was patronised was an understatement.

      P.

    10. Re:Colour depth. by Anonymous Coward · · Score: 0

      Yeah, it is real difficult to google for "postgresql "show databases"" and click the first hit.

    11. Re:Colour depth. by dozer · · Score: 1

      I hate to tell you... As long as Carol has gimp.org in her email address, she DOES represent the Gimp project. And she continues to be a major problem. I can't believe you guys are still waffling over this... Any other project would have revoked her email address after the first stern talking-to.

    12. Re:Colour depth. by Anonymous Coward · · Score: 0

      I'm glad to see I'm not the only one, by the responses here. Carol hasn't really abused me, but sent mail after mail rambling on about how she does this free support for the gimp and isn't being paid for it. At least I think that's her complaint, but I can't be sure it's really a complaint as she skirts around a hundred issues in her emails all to do with being taken advantage of, putting effort into gimp and having other people control her life.

      I made the mistake of responding to her a few times and I think she clung on tight since then. Any email from her goes to /dev/null now anyway including list email. No matter how bad she is if you don't see what she's going on about it can't get to you. Or confuse you. That's all too easy these days anyway but I don't need anyone helping me.

  74. Ugh. by jd · · Score: 0
    16bpp seems... crude. Besides, there should be nothing in the palette that can't be produced in a 24-bit mode, since it's just a table of RGB values. Well, unless you've an alpha channel OR a layering channel, in which case you need a 32-bit mode. If you have both, you're into the 40-bit realm, and I'm almost certain there are no packages which support that.


    If you add in support for tetrachromats (hey, why should we encourage discrimination?) and IBM's polarized monitor, we can get to 96bpp without much trouble. I'm sure, with some inventiveness, we can round it up to 128bpp quite easily.


    Now, doesn't a 128bpp image editor sound sooo much cooler and geekier than a paltry 16bpp? Besides, with broadband taking off, we've got to soak up the excess bandwidth somehow.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Ugh. by fossa · · Score: 1

      16 bit typically refers to 16 bits per what I'll call a sample. 24 bit RGB has 8 bits per sample, 3 samples per pixel. 16 bit samples would be 16x3 = 48 bit RGB.

    2. Re:Ugh. by ipfwadm · · Score: 1

      16bpp seems... crude. Besides, there should be nothing in the palette that can't be produced in a 24-bit mode, since it's just a table of RGB values.

      He meant 16 bits per SAMPLE, not 16 bits per PIXEL. DSLRs and some point-and-shoots offer the capability to save files in raw mode rather than JPEG. Canon's sensors are 12 bits per sample I think, and the raw images can be decoded into 16 bit per sample TIFFs. Versions of Photoshop earlier than 7 had minimal 16-bit support, but the latest version of PS has not only much better 16-bit support, but also native support for many camera manufacturers' raw formats.

      So no, nobody wants 64k (16bpp) color, that was so 1994. They want 64k^3 (48bpp) color.

    3. Re:Ugh. by AaronW · · Score: 4, Informative

      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.
    4. Re:Ugh. by NoMoreNicksLeft · · Score: 1

      When he says 16b, he means per color channel. Effectively 48bit color. Some high end cameras apparently capture images at this depth. Crude isn't a word I'd use to describe it.

    5. Re:Ugh. by Prune · · Score: 1

      You dumbass, this is about 16 bits per pixel, so each of R, G, and B channels is 16 bits. 8 bits per channel is problematic because in general image processing operations reduce the dynamic range, so the 8 bit quantization is insufficient, even if it's all that a non high-dynamic range display can show. Now add to this the fact that HDR displays are already starting to come to market (even if still over $50K), even 16 bit per color may become insufficient.

      --
      "Politicians and diapers must be changed often, and for the same reason."
  75. GIMP has aways served me well... by Dan93 · · Score: 1

    For my job, I've never needed a graphic program other than the GIMP. IMO, it works just as well as photoshop.

    1. Re:GIMP has aways served me well... by Anonymous Coward · · Score: 0

      "For my job, I've never needed a graphic program other than the GIMP. IMO, it works just as well as photoshop."

      Your job doesn't include serious print photography, and your output doesn't have to be publication ready, correct? Your work isn't under a contract that specifies how color will be calibrated, right?

  76. From My Experience by pjludlow · · Score: 2, Insightful

    I've used Photoshop for around 10 years now. My last two jobs were jobs were I used Photoshop full-time. Needless to say I use it a lot and feel like I'm qualified to express my opinion about it. You should also know I have never used Gimp. I'm running on OS X, and I know I could install it if I wanted, but I don't see a point. Photoshop is the industry standard in graphics, and no one will care if I'm fluent with the Gimp on a resume (that sounds odd in any case). I've also spent countless hours on figuring out how to do what I need in Photoshop, and I'm not going to throw that away by saving a few bucks ($150 for upgrade, or $500 for full version) by using Gimp instead of Photoshop. The time I would lose figuring out the "quirks" in Gimp wouldn't even justify me thinking about it. OSS is great, I use a lot of little utilities on my mac that come from those efforts. I don't make a profession by using any of them, but they enhance my experience and make my life easier. I really don't see OSS making inroads in the graphics industry though. It's a cycle because Photoshop is the standard, companies hire those that know how to use the standard, schools teach students how to use the standard so they can be hired, and Photoshop continues to be the standard because it is used and taught everywhere. How do you combat that? I applaud the efforts of the OSS community creating Gimp but I think it will always stay in a niche outside the limelight.

  77. I need non-destructive layer effects. by Anonymous Coward · · Score: 0

    Right-click on a layer in Photoshop, select Blending Options. An assortment of layer filters that can be reversed at any time.
    It's been in Photoshop since forever, and Gimp still doesn't support it, or have anything like it.

  78. SDI my ass. by Mikey-San · · Score: 1, Insightful

    While I don't think GIMP is a complete Photoshop replacement, I gotta call bullshit on one of the article's reasons.

    Saying that one of the reasons GIMP isn't a [Photoshop] replacement is because Photoshop is a single-document interface completely ignores the fact that the Mac OS X version of Photoshop is a multiple-document interface, just like GIMP.

    Another hastily written article posted to Slashdot. Nothing to see here, move along.

    --
    Mikey-San
    Karma: +Eleventy billion (mostly affected by watching Celebrity Jeopardy)
    1. Re:SDI my ass. by Nadir · · Score: 1

      Everyone critices GIMP's interface and the fact that it is not MDI like Photoshop on Windows.
      I absolutely hate Photoshop's toolboxes !!! I'd rather have the side panels like InDesign has, so they can be easily hidden.

      --
      --
      The world is divided in two categories:
      those with a loaded gun and those who dig. You dig.
    2. Re:SDI my ass. by Kelson · · Score: 2, Insightful

      But do MDI and SDI really exist in the same way on the Mac as they do on Windows? Having a single menu bar at the top of the screen makes a big difference.

      Photoshop on a Mac and a maximized Photoshop on Windows work almost exactly the same, as far as the user is concerned. The only difference is that on Windows you get a flat background behind everything, whle on Mac OS you can see the desktop in the background.

      Sure, if you've got other apps open, you can mix-n-match, but for the base case of one app open with multiple docs, it's nearly identical.

    3. Re:SDI my ass. by KayosIII · · Score: 1

      No this is accurate You wouldn't believe how many times requests to make gimp MDI go through the gimp lists and everytime it is brought up on the web. It appears that there are a lot of people out there who have only used the PC version of Photoshop. What needs to happen is either it goes MDI or the SDI becomes as smart as it is for Photoshop on the Mac.

  79. Nobody likes to say GIMP by Quadfreak0 · · Score: 1
    large size / high quality and industry standard problems aside, the name GIMP just doesnt blend well in a pro/corp world.

    Sure it's a fun name and all but when you're asked what software you use gimp sure as hell better be second or third on the list right below photoshop/illustrator.

    Lets play a game, pick the one that doesnt fit
    1)Photoshop
    2)Aperture
    3)Gimp
    4)Paintshop Pro
    5)Cripple

  80. You all miss the idea behind editing native 16bpp by gorim · · Score: 1

    The issue is now directly working in RAW, I didn't state that very well. I want to import from RAW (which is possible) and keep it in the native 16bpp.

    The reason ? Because a workflow for processing digital photos can involve applying quite a few filters and transformations. Doing as much as possible in 16bpp is more likely to prevent visible artifacts from occuring. Then, when one is all finished, the final product can be converted to 8bpp for either printing or web posting.

    If one goes straight to 8bpp and then applies all of the filters and transformations, artifacts are more likely to creep into the image along the way, and those can be annoying to deal with.

  81. Linux by PenGun · · Score: 0

    Here is the deal. If you love computers you end up enjoying "hacking the hardware". It is really the bottom line, getting the hardware to do what you want it to do. So really ... who cares with a printing app. It's not like it's all that hard to do, getting a printer to print. Although that is the reason RMS lost it and created Free Software.

      It is an experience windose users will never know. It is not trivial to get hardware you have no handle on to do what you want.

      The photoshop - gimp thing is kinda dumb. You need 4 color printing and Pantone complient colors you pay for the Pantone license. If not you are probably a fool to pay for something you don't need.

        PenGun '
      Do What Now ??? ... Standards and Practices !

  82. By this logic, by robotoverflow · · Score: 1
    all software should have the exact same interface as every other in its own category. Editors, 3D modelling and animation software, you name it.

    To adopt this kind of design policy we should dump KDE and GNOME right this second so we can focus on making an exact clone of the windows interface for unixes. After all, the people who already use the alternatives are only in the minority. It doesn't matter in the least if those users are forced to relearn everything at the expense of people who find it hard to learn how to use differing interfaces.

    We must only accommodate the majority.

    --
    % mkdir :
    % ls -dF :
    :/
  83. not to be politically incorrect but, by pair-a-noyd · · Score: 0, Flamebait

    "gimp" is also slang for someone who is crippled or handicapped.

    http://www.answers.com/gimp&r=67
    The noun gimp has one meaning:
    Meaning #1: disability of walking due to crippling of the legs or feet
          Synonyms: lameness, limping, gimpiness, gameness, claudication

    Could it be??

    Personally, I've found gimp to be pretty limited. Sure, it can do a few neat things but for the largest part, it's pretty darn limited.
    Way back when when I was using M$ winders I had taken a liking to Paintshop Pro.
    As they upgraded through numerous revisions I found that out of all of them, I liked the 6.x version the best. I don't know what version they are up to now but sometime back I tried to get 8.x (I think) working under WINE and had no luck.
    I then played with it on a winders box and decided that I didn't like the newer version.

    I tried to find the 6.x on http://www.oldversion.com but no luck.

    As for photoshop, I never cared too much for it, the price is insanely high and it's massive overkill and overly complicated for the basic stuff I play with on occassion.

  84. First you need color management by Anonymous Coward · · Score: 0

    I tried to use Gimp on Linux, but the color management story was pathetic. There are bits and pieces, but you can't calibrate a monitor and you can only calibrate some printers.

    You can't do serious photography without color management. Gimp users may live with this, but Photoshop users expect this to work right.

    -Dan

  85. MS-Access by Tablizer · · Score: 1

    Bash MS-Access all you want, but there is very little in the OSS GUI world that comes reasonably close to replacing it. This is a shame since it has a lot of ways it can be bettered because it has more holes and oddities than Martian swiss cheese.

    And it is a common tool. It is found almost anywhere that ad-hoc data manipulation or quicky single-user forms are needed. There may be better commercial products for a company to purchase, but since it is bundled with "advanced" MS-Office, they use it instead because it is there and "good enough".

  86. Game dev by kreyg · · Score: 2, Interesting
    I use the GIMP from time to time in game development (as much as a programmer needs to anyway).

    Likes:
    -Supports a wide range of file formats
    -Tons of image editing and processing options
    -Understands the concept of an alpha channel
    -Free!

    Dislikes:
    -Alpha channel support is "inadequate" (to be kind)
    -8 bits per channel max
    -Starts up very slowly

    I don't hate the interface as much as some people, but then I don't work with it all day either. I imagine the bits-per-channel thing could be a pain to fix, depending on how things have been designed. It seems that most problems with it are known and fixable, why is it exactly that they aren't?

    --
    sig fault
    1. Re:Game dev by The+MESMERIC · · Score: 1

      Gimp starts extremely fast. But on Linux. Maybe its Windows because it has to load the GTK libraries and all.

    2. Re:Game dev by kreyg · · Score: 1

      Yes, it is Windows. I don't think it's GTK though, mostly it seems to be searching for plugins or loading components.

      --
      sig fault
    3. Re:Game dev by The+MESMERIC · · Score: 1

      in my Linux it opens extremely fast - seriously not being biased here. which is why sometimes i rather open something in gimp than on emulated photoshop (win4lin or wine)

  87. Why isn't there a Linux build of photoshop? by jesterzog · · Score: 1

    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.

    ...which does cause me to wonder why Adobe hasn't released a Linux build or two. Considering how popular it is, I would have thought there was quite a serious market of people wanting to run Photoshop in Linux, and that might make it worth doing even if it wasn't a trivial port.

    Does Adobe have some conflicting interests here that I've missed?

  88. What is on the rest of the list? by Tablizer · · Score: 1

    Okay, so PhotoShop is #1 on the list. But what about #2 thru #9? (I guessed in another message that MS-Access is on it.)

    1. Re:What is on the rest of the list? by Tablizer · · Score: 2, Informative

      Never mind. I found it:

            1. Photoshop
            2. Autocad
            3. Dreamweaver
            4. iTunes
            5. Macromedia Studio
            6. Flash
            7. Quicken
            8. Visio
            9. Quickbooks
          10. Lotus Notes

      I am batting zero today. Time to sleep.

  89. GIMP worst file open/save dialog box ever by Anonymous Coward · · Score: 0

    My two main gripes,

    * GIMP worst file open/save dialog box ever

    * Text tool is nearly useless

    1. Re:GIMP worst file open/save dialog box ever by daverabbitz · · Score: 1

      > My two main gripes,
      >
      >* GIMP worst file open/save dialog box ever
      I assume you are referring to GIMP for windows. I'm using Gimp 2.2 on Gentoo, and it uses the Gnome file requestors which IMO are the best file requestors ever. I have used the windows version and have to agree that the windows requestors suck hard.
      >
      >* Text tool is nearly useless
      I agree, it is very light-weight, however I don't see this as much of a problem. Generally if I need to do titles or banners I use inkscape, GIMP is generally the wrong tool for the job in that situation.

      What I'd really like to see would be colorspace independance (CMYK, Float, Arbitrary sized palette), that, and macro recording.

      --
      What could be better than a jet powered motorcycle? http://www.youtube.com/watch?v=u8l6GTHLSWE
  90. Re:What is on the rest of the list? (correction) by Tablizer · · Score: 1

    correction: I meant 2 thru 10, not 9.

  91. sucks by Anonymous Coward · · Score: 0

    Cause GIMP fucking blows? I may be biased, as I've been using Photoshop for 6+ years, but Photoshop has one of the most intuitive tool sets I've ever used (and I've used an awful lot of software), and GIMP has one of the most unintuitive. I found it far too difficult to perform even simple operations in GIMP, knowing exactly what I wanted to do. Obviously, most people are going to have to switch over from PS to GIMP if it is a big deal, so they should make the transition much easier.

  92. I Love the GIMP! by alabamarasta · · Score: 1

    I have watched the GIMP get better and better. I like the GUI which is flexible once one gets the hang of it.

    I cannot afford Photoshop.

    I believe many people don't like GIMP because they have not spent enough time with it to get the hang of it.

    More people I think would like it if they knew how easy it is to get.

  93. Add Cocoa and Carbon to Wine? by BluBrick · · Score: 0

    Is it just me or does that prospect make anyone else feel like blowing chunks?

    --
    Ahh - My eye!
    The doctor said I'm not supposed to get Slashdot in it!
  94. Here's what's really missing from GIMP by melted · · Score: 1

    1. 48 bit color.
    2. Full color management, including soft-proofing and conversion into profiles.

    That's about it for me. If it had just these two things, I'd put my copy of Photoshop CS2 on ebay.

    1. Re:Here's what's really missing from GIMP by tigersha · · Score: 1

      Here are a few more:

      Save for Web
      Integration of Vector Stuff into the bitmap as a Layer
      Layer Styles
      Text editing on the bitmap (what's this text in a dialog box crap???)
      Slices
      Adjustment Layers (This is killer, it makes PS more like a spreadsheet)
      CMYK (No, a "rudimentary" plugin does not count)
      The integrated file browser
      Actions (yes, Gimp is scriptable, but actions are easier to handle for quick jobs)
      Good Typographics control.

      These are all useful things for the "Quick Web Button" crowd (like me, 80% of the time). And even that Gimp does waaaaaaaaay worse than Photoshop. Gimps problem is that its handling sucks, irrespective of the whole right-click MDI/SDI fracas.

      A companion Vector drawing program (Illustrator is GREAT)
      There is also the Indesign business w2hich PS work well with.

      No neecessarily PS strenghts, but strengs deriving from the fact tha tPS is part of a suite.

      The problem with Gimp is not that it does not have the features (which is what the FOSS whackos always spews). It mostly deoes have the features, but the program is simply clumsy.

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
  95. ...it's because by Anonymous Coward · · Score: 0

    ...other linux using people bothered to fill out the form at Novell and indicate what they want. The results and list speak for themselves. It's about as democratic as you can get. Who are you to maintain someone doesn't need or want some software on linux? If you don't want it or need it, that's fine, this effort to identify apps that currently don't run on linux is not your cup of tea, so why bother with the not very well hidden insults?

    Now, me, in my not even close to humble opinion, I'd like to see a list of apps that were made IMPOSSIBLE to run on linux! Or ANY platform! Starting with FLASH, which has to be hands down the most abused and annoying thing on the intarweb today. I don't want to block it, I want it GONE, I don't want one more poor human to have to suffer a single flash based anything, it's like animated GIF meets and breeds with The Terminator, it just keeps coming and it HAS NO PITY. ;)

  96. The Gimp is just as usable as Emacs! by Anonymous Coward · · Score: 0
    I hate to say it, but I find the Gimp to be almost unusable. I'm sure that if I learned where everything is on it, it would be as easy to use as, say Emacs.

    ---------
    File upload and sharing

  97. Gimp and Photoshop by vdammer · · Score: 2, Interesting

    Interesting that so many people complain about Gimp's interface compared to Photoshop's. I use Photoshop professionally, and have it set up with two monitors; the toolbox and images go on the primary monitor while the rest of the palettes go on the second monitor (I use this setup on Windows and Mac machines). I use Gimp at home, and have the same setup.

    So what's all this about Gimp's interface being inferior to Photoshop's? In both cases, the default interface configuration is about the same, and I do about the same amount of work to get my personalized interface. I also change hotkeys for both applications to my own preferences. It's easy to do on both applications.

    Best not complain about something until you try it--really try it, don't just load it once and then bitch about it.

    When it comes to working with digital photos, I can go with either program. I've made professional-quality prints with both programs, and for the most part, Gimp's 8-bit limitation isn't really a hindrance if I get my raw settings right with my raw converter. Color management? It's coming along nicely in the development version. No worries here.

    For everyone who wants high-bit depth and other color spaces (this includes me): if you know how to code, get in there and submit patches to the various programs that will eventually perform all of this number crunching for Gimp. If anything, I'd like to see an updated roadmap for GEGL and GGGL and all the other programs that are being worked on right now. Hopefully someone will have time to write up such an overview so the rest of us will have a better idea what's going on.

    All that aside, Photoshop or Gimp can be used professionally, and both are just about completely interchangeable. Give Gimp some time! Its developers aren't full-time paid programmers. They're volunteers, and they're doing a damn fine job.

    1. Re:Gimp and Photoshop by Hosiah · · Score: 3, Interesting
      You're too smart. What are you doing posting to Slashdot? (-:

      Incidentally, I just happened to have refuted the inaccuracies in the TFA here. Perhaps you can point some of these out to others in this forum? Or add to them over time? I, too, have experience with both (as well as with MGI-photosuite, Macintosh Draw, Windows Paintbrush, xfig, and Corel Draw, and more I've probably forgotten), and am absolutely baffled at how so much flat-out Bull gets spread about one little program. I'm getting to where I have a pet theory that Steven J. Vaughan-Nichols is the source of all of it!

      But anyway, you being a user of both, I would highly value any input you could provide in the comments sections of my blog's tutorials (scroll down the menu on the left, they're there). I'm fine with porting Photoshop. I'm *not* fine with the mythology going around.

  98. Is this really a surprise? by Joe+Decker · · Score: 2, Interesting
    Hmmmm. Last April when we last talked about this, I listed as major hurdles to GIMP replacing Photoshop features including "16-bit" images, adjustment layers, CYMK processing and (with a little help from a commenter at that time) color managment.

    (I'd also incorrectly guessed that RAW processing wasn't available at all.)

    My understanding is that none of those features is yet addressed, although CMS is due in GIMP 2.4.

    In that same time frame, PS has made advancements itself.

    I, for one, welcome our new Adobe..., errr, that is, I remain unsuprised by corporate users wanting PS-on-Linux.

  99. Don't kneejerk-bash Irfanview/GUI's by Mathinker · · Score: 1

    See:
    File->Batch Conversion/Rename->Set Advanced Options

    Wow! I didn't know that RTFA could also stand for "Run the F***ing Application"!!!

    I love scripts myself, but don't be a "kneejerk"...

  100. Sorry, yeah, I meant 16 bits / color channel by gorim · · Score: 1

    16 bits each for R, G, and B.

  101. Linux is great, at what it can do... by matgorb · · Score: 1

    First of all, I'm a Linux user, I have a Linux desktop, but I know how difficult it is too talk about the desktop with the Linux crowd. Most of us/them think that Linux is so good, both technically and morally, that it will just make its way to everybody's desktop without the need to adapt to whatever the wannabe Linuxes have to say. Most of the time you would get something like, why would you want that, if you do, stay with your [insert swearing] Windows (funny whan you use Mac OS X). Anyway the point is that a lot of the so called Linux advocate, at least the more vocals, don't want their cherished OS to be tainted by popular commercial apps. Let's face the truth, most of the Linux users use Linux to build a better tool for themselves, their computer, while what the pro users discussed here, creative people, really want is the tool to be ready to work. Today still, the difference between using Linux and Win or OS X, is the same in spirit as using a home built-pc or a mac (or a dell if you wanna strech it) On one hand, you'll have to spend time to get everything working, and the people doing it like it, and on the other you will plug, and play, and that's what people working with computer as a tool and not not an end want. Linux desktop has its place, the geek users, the "poorer users" (Look at the real goal of Ubuntu=>Linux for African users), the corporate write and mail users, but if it wants to get to other places, it will have to listen, and in the Linux world it is very difficult to be listen to if you don't wanna write code or submit bug, that's all.

  102. Ah! by jd · · Score: 1
    Now that's a different kettle of fish. (Though I would have preferred it if the other posters had considered the fact that I can't read minds as easily as I can read posts.)


    16 bits per channel is much better. I still think the number of channels is limited, though. When you get right down to it, it would not be hard to have an image editor that supported stretchy integers for however many bits you wanted in the channel, and no hard-coded limit on the number of channels. (Although you'd presumably need a plug-in for channel types that were unknown.)


    Well, I guess I'll add this to my long list of "things somebody, somewhere, really should do but it looks like nobody else is going to be bothered for a while". I worked on a very similar problem a long time ago and I vaguely remember the solution I used. At the very least, I should be able to put together something that'll work with images of arbitrary complexity.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Ah! by gorim · · Score: 1

      Its more than just a completely different kettle of fish, professional and many non-professional photographers routinely, often exclusively (if they have control over it), operate solely in 16 bits / color channel. They do this for all of the reasons I explained before, performing all filters/transformations in 16bit/channel to avoid the gradual introduction of artifacts before a final conversion to 8bit/channel at the end.

      Pretty much any other package that caters to this class of users offers this capability. GIMP, on the other hand, has no interest to offer this as a feature. Thats fine, but then there is a whole segment of people who will end up going over to Photoshop and a mix of other applications.

  103. Re:In other news... you are full of it by Sycraft-fu · · Score: 2, Informative

    Photoshop 9 (CS2) runs just fin on a computer with 256MB of RAM. On a system with a gig, it screams. It does not make you configure scratch disks, and so on. It's easy of use is so far above GIMP's it's not even funny. Had you actually spent any amount of time using Photoshop and looked at it objectively, this would be pretty obvious.

    Please, let's cut the crap. This kind of overly optimistic "The opposition sucks, our solution is the best!" is stupid and hurts OSS. The reason it hurts it is because if someone actually listens to you and trys GIMP, expecting it to be better than Photoshop and then find out it's not, they get a very negative impression of OSS. They believe that it's all a bunch of shoddy shit created by amatures, and that the things they hold up as the best products are, in fact, poor quality.

    GIMP is fine for people who do non-serious work and are willing to put up with a difficult interface to get what they want. It's not easy for beginners. For that, there's Photoshop Elements.

  104. bunch of whiners by idlake · · Score: 0, Troll

    Photoshop didn't use to have 16 bit/channel images, and apparently it was good enough for "professional" use back then.

    There is legitimate usability complaints and then there is whining. There are legitimate usability complaints one can make about both the Gimp and Photoshop. But the dislike of those vocal "professionals" for the Gimp is mostly whining: they aren't willint to learn anything that's different from what they are used to.

    Let these people stick with Photoshop on Windows and pay a significant part of their earnings to those copmanies. Sooner or later, a new generation is going to figure it out.

  105. Only the Gimp's success can bring Photoshop by donscarletti · · Score: 1
    This whole stupid discussion misses the point completely. What can Joe free software developer, or even Joe loud mouthed open source pundit do to get Photoshop ported to Linux? Can he download the source from Adobe and port it himself? Can he put up a $500 bounty for anyone who does it? Nope.

    The only people who can possibly do it is Adobe. Adobe is not a Linux hostile company, they have ported things to Linux before, but only when it helps them make money, expected sales are what they care about. What Adobe sees is a platform that no graphics designers use, and only 10 million or so people use at all worldwide. What would be the point of porting photoshop? None at all!

    What could make Adobe want to port photoshop to Linux? Artists using Linux; that's what. How can Artists start using Linux? Improving The Gimp and marketing the Gimp, because like it or not, the gimp IS graphics under linux. Get your head out of the fucking clouds for a second and think about what you can do. If you ever want to be free of Gimp under linux, go right home and make a patch making the Gimp better then tell all the creative types you know: "Gimp rocks and you should use it and Linux for the best art experience".

    Bitching and moaning about the gimp is pointless because it is all we have and all we can improve. If Gimp developers start getting discoraged by reading about how much photoshop kills gimp in every way then you will NEVER have photoshop under Linux. However it is a lucky fact that no useful developers of any project read slashdot unless they can help it.

    --
    When Argumentum ad Hominem falls short, try Argumentum ad Matrem
    1. Re:Only the Gimp's success can bring Photoshop by shmlco · · Score: 1
      "What Adobe sees is a platform that no graphics designers use, and only 10 million or so people use at all worldwide. What would be the point of porting photoshop?"

      Not to mention the fact that it's a platform whose users, well, let's just say it's one whose users PREFER not to pay anything for software at all.

      What's my incentive again?

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    2. Re:Only the Gimp's success can bring Photoshop by Recovery1 · · Score: 1

      "Not to mention the fact that it's a platform whose users, well, let's just say it's one whose users PREFER not to pay anything for software at all."

      You're talking about the windows world right? I can't even recall all the times I walk into homes and businesses to fix their windows computers and find "warez" programs installed and being used on a daily basis.

    3. Re:Only the Gimp's success can bring Photoshop by Fred_A · · Score: 1

      I don't know about others but I certainly don't mind paying for software. I have to admit I don't currently have any commercial Linux software (haven't found any I needed, used to have Applix Office a long time ago though) but I still have a gaming partition which at any given time hosts 2 to 4 store bought games.

      If something like Aperture was released for Linux for example, I'd certainly consider it.

      I'm not against commercial software as such. Apart from the FOSS aspect, I currently run Linux on my desktop because I find it easier to use than Windows or MacOS and because it makes it easier to avoid vendor lock-in for my data. If I find some commercial software that can help me work better/faster and won't lock my data, I don't mind paying someone for it.

      I know there are a number of FOSS users that are either maniacs that are completely against commercial software "à la RMS" or that are just freeloaders, however all in all I think that most of us actually have more respect for licences than users of commercial systems.

      So while you will see "pirated" software on most Windows PCs, those which were mostly used as Linux/BSD/whatever machines (or which were spare machines to a FOSS box) had much less than usual.

      Just what I've seen though, it might not reflect what happens around you. :)

      --

      May contain traces of nut.
      Made from the freshest electrons.
    4. Re:Only the Gimp's success can bring Photoshop by Kadin2048 · · Score: 1

      Not to mention the fact that it's a platform whose users, well, let's just say it's one whose users PREFER not to pay anything for software at all.

      I would have said this differently:

      Linux is a platform where there is a wide perception that its users will not pay for software.

      Whether that perception is beared out in reality, is another thing entirely; there does seem to be a certain amount of truth to it (go do some Google searches for Cedega and you'll see some of the problems they have getting people to cough up $5/mo), and I think that Linux by its nature (free as in beer as well as free as in freedom) does attract quite a few people who are, frankly, cheapskates -- the kind of people that you hear saying things like "if I wanted to pay for software, I would have used Windows!" -- but I think it's also a lack-of-evidence problem because there aren't too many commercial software packages for Linux, outside of niche markets, thus it's nearly impossible to disprove.

      I'm not exactly sure how we change this, as a community (or if we'd want to if we could). Obviously a big selling point of Linux is that there is a large software base which is free-as-in-beer.

      I think the GGP (at least I think that's who it was who said it, somewhere higher up in the thread anyway) who said that what we need to do to get commercial software on Linux is increase userbase, and the best way to increase userbase is by having better free tools. That's, I think, probably the only way to break the chicken-and-egg problem that now exists. The thing that will bring commercial developers to the platform most quickly, is if there's a viable alternative to their product available on it for free. When they see it starting to cut into their marketshare, then they'll want to have a presence on the platform.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  106. Photoshop users are amonst the most stubborn by KayosIII · · Score: 2, Interesting

    I am somewhat of a graphic professional and a Gimp user. While the GIMP does not match Photoshop feature for feature neither does it cost $1400 (the local cost).

    I have long had difficulties regarding other designers and photoshop. I am self taught Photoshop was purhaps the 3rd graphics app I learnt, for most I suspect it is the first and last. It is not just the gimp that suffers from this it is just about every graphics app out there. For instance I read a magazine review of the latest version of Paint Shop Pro the only negative thing they could say about it was "it's not photoshop". I have known users who stubbornly have waited years for photoshop to gain a feature rather than use another tool which is built for the job they are trying to do. I will admit however there are some jobs where photoshop *is* the best choice.

    Finally if you really could see yourself using linux but for photoshop. Write a letter to Adobe - Adobe wants to see that there is a market before they port. I don't think much else is going to convince them.

  107. Fonts in OS X? by grrrl · · Score: 2, Interesting

    erm last time I loaded up the GIMP I couldn't even use any of the OS X fonts. Maybe you can (can you?) but that's a pretty big reason to use it for home-graphics use (ie when you can't afford/need photoshop). I'm pretty techie but I just couldn't be assed after 10 mins of googling and turning up no answers.

    1. Re:Fonts in OS X? by Ford+Prefect · · Score: 1

      erm last time I loaded up the GIMP I couldn't even use any of the OS X fonts. Maybe you can (can you?) but that's a pretty big reason to use it for home-graphics use (ie when you can't afford/need photoshop).

      Gimp.app will make use of installed OS X fonts by default, but the list is somewhat polluted by rarely-used variants used for far-Eastern languages and similar, and irritatingly it doesn't pick up on the different styles available for some fonts. I think I'll report a bug... ;-)

      --
      Tedious Bloggy Stuff - hooray?
  108. 16 bits per channel by dimss · · Score: 1

    The only thing I miss in GIMP is ability to use 16 bits per channel. This is a must for quality photography and especially RAW image processing. There is ufraw plugin (dcraw-based) which processes RAW images internally at higher color-resolution and produces 8-bit image. This is partial solution.

    Some time ago, there was a project named GEGL which could give as 16-bit in GIMP. Are they alive?

  109. GimpSHOP by IYagami · · Score: 1

    There is an alternative about the GUI for GIMP: it makes GIMP similiar (in a certain way) to Photoshop: http://plasticbugs.com/?page_id=294

  110. Yeah, like rezising a brush for instance! by Kristoffer+Lunden · · Score: 4, Interesting

    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.

    1. Re:Yeah, like rezising a brush for instance! by Tet · · Score: 2, Informative
      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?

      Given that ctrl-k is used for similar functions in other applications, it's fair to reuse it for that in Gimp. ISTR that even MS Excel uses ctrl-k to clear a cell, for example. Note that it's trivial to remap the delete key to either cut (normally ctrl-x) or clear (normally ctrl-k) in Gimp, should you wish to do so. You could argue that it should perhaps be the default setting.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    2. Re:Yeah, like rezising a brush for instance! by hawk · · Score: 1

      It deleted cells, rather than clearing them.

      Then, suddently, a couple of years ago, a command that had deleted cells for over a decate got remapped to "insert hyperlink"--in a spreadsheet, for crying out loud!

      hawk

    3. Re:Yeah, like rezising a brush for instance! by ChiliJ · · Score: 1

      Not only that, brush sizes are limited. If working on a larger image or needing a larger brush, there appears to be no choice but to create a larger brush?

    4. Re:Yeah, like rezising a brush for instance! by Anonymous Coward · · Score: 0
      Note that it's trivial to remap the delete key
      Users shouldn't need to remap key to make an app not suck. The app should not suck by default! (With thanks to mpt.)
    5. Re:Yeah, like rezising a brush for instance! by Tet · · Score: 1
      Users shouldn't need to remap key to make an app not suck. The app should not suck by default!

      That's all a matter of perspective, though. By that definition, Photoshop sucks because it uses unintuitive (to me) key mappings.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
  111. They would need to sell 100,000 copies by Cid+Highwind · · Score: 1

    I'm sure that they'd sell many more than a few hundred copies to the Linux market. Maybe even a thousand.

    $800 x 1000 copies = $800,000

    A dinos^H^H^H^H^H company the size of Adobe would blow 800 grand just on meetings to discuss ways to get every employee a new 3-ring binder with amended versions of the corporate software licensing policy and equipment procurement standards with the necessary changes to allow developers to requisition Linux machines for preliminary development of a Photoshop port...

    --
    0 1 - just my two bits
  112. GIMP vs ACR, Lightroom, CS2 by Builder · · Score: 2, Insightful

    What spending 600 quid on Photoshop gave me was hours of my life back. Ignoring the technical issues like 16bit support, LAB, plugins, etc. I still would have spent this money on CS2.

    Being able to modify exposure, black point, contrast and white balance in a second or two per image cut my workflow on a standard shoot from about 2 hours to 1 hour. Beign able to do that non-destructively so that I can go back and try something else later is even more valuable. Cutting my time down behind the machine means I can spend more time behind the lens, and that's where the money really is.

    Being able to make a change once and then copy it to every other image in the shoot, or a selected subset of those images means that I don't make mistakes.

    The other big issue is information available. Adobe Photoshop CS2 for Photographers is an awesome book. It presents 'recipes' that are easily understood, achieve a specific goal and can easily be turned into actions. The Real World Camera RAW book was also fantastic.

  113. "PC LOAD LETTER"? What the fsck does that mean? by BigBlockMopar · · Score: 1

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

    Oh boy...

    Along those lines, did you know that the PC LOAD LETTER error can be changed on most LaserJet II/III models? Maybe like "OUT OF LETTER" or "FEED ME A4". I still encounter these things in offices, and I still see one of the most cryptic error messages ever written. Exact proof of your statement: sensible defaults are essential, most people never figured out how to set the clocks on the VCRs; there's no way they can handle something like customizing a menu.

    Years ago, I wrote a big long rant on why Linux isn't ready for the desktop; the GUI for virtually everything in Linux sucks. "Designed by geeks, for geeks" works great for admin-type stuff, but absolutely not at all for Joe Sixpack or PHB's e-mail client.

    My original rant, only slightly appended over the years.

    Until the Open Source community actively recruits user interface experts, we will never get Linux out of the server closet.

    --
    Fire and Meat. Yummy.
    1. Re:"PC LOAD LETTER"? What the fsck does that mean? by Anonymous Coward · · Score: 0

      Out of interest, have you ever seen Syllable? Not because it has a good user interface or anything (It doesn't, yet) but because they're not doing "Designed by geeks, for geeks".

    2. Re:"PC LOAD LETTER"? What the fsck does that mean? by BigBlockMopar · · Score: 1

      Out of interest, have you ever seen Syllable? Not because it has a good user interface or anything (It doesn't, yet) but because they're not doing "Designed by geeks, for geeks".

      Well, it sure is pretty, and I like the fact it's got Unixish guts!

      Of course, only time will tell whether or not anything useful will come of it - based on a quick read, I think there's gonna have to be a lot of work to make it run Linux stuff out of the box, since at least that will give it a software base to start with.

      --
      Fire and Meat. Yummy.
  114. what about simple automation tools by melekzek · · Score: 2, Interesting

    Although we can argue that scheme based scripts in gimp are "potentially" more powerful than recording actions in PS, for most of the time, simple recording can do the job. Now, I need to open a bunch of files in a given directory, apply a serious of filters, and save. In PS, I can do this in a second. In gimp, I have to write scheme code, debug somehow, which takes far more time than doing this in PS. Not that I do not enjoy writing functional code (i used to be in love with caml), but I do not think that the artistic community will share my love.

  115. Don't be different, okay? by saikou · · Score: 3, Insightful

    I tried GIMP. I spit four thousand times and I went back to Photoshop. Yes, interface is customizable and simply takes "getting used to" but I don't want to customize nor get used to it, all I wanted was to make a small animated toolbar (which I did in less than 10 minutes at home). Why can't there be a version that does things like Photoshop does?
    I think GIMP is in the same UI trap as Lotus products that are trailing Microsoft Office popularity -- "We're different, and we don't care that more popular product has different interface, we'll force users to get used to ours". Yes, there will be perver strange people who will say they like Lotus UI because "it's different" but for most people Microsoft Office interface works, and Microsoft got where it is now not only because of the monopoly tie-in with OS products, but because they copy good things into their products, including UI. By being "different" Lotus office products limited themselves to situation where user is forced to use them. And for home they run for Word or for something that looks and behaves like Word.
    Every time you encounter radically new interface it takes time and effort to get used to. People don't want and don't have to do it. Leave the radical and ugly dysfunctional interface to hobbyists, and copy Photoshop interface for the rest of users. If you want to make a point how easier/better GIMP interface is, add a little window that says "You could have easily done it in GIMP native interface by pressing blah blah blah". And, perhaps, allow pieces of interface being switch to native mode, so once user is completely accustomed to GIMP way of doing things whole interface would be reverted to radical mode.
    Instead of that all I see is people argue with foam at their mouth on how much better GIMP interface is.

    1. Re:Don't be different, okay? by cortana · · Score: 1

      It's called Gimpshop.

  116. GIMP can't even draw rectangles by Anonymous Coward · · Score: 0

    To draw a rectangle in GIMP you have to do some nasty tricks with masks. Hardly anything a beginner would expect. I'm still having difficulties understanding why the GIMP developers refuse to provide some basic bitmap editing possibilities like one finds in paint for windows 3.1

    1. Re:GIMP can't even draw rectangles by arevos · · Score: 1

      Select a rectangular area with the select tool. Click the 'selection to path' button, then the 'draw path' button. Not exactly that direct, I'll agree, but there's no fiddling around with masks required.

    2. Re:GIMP can't even draw rectangles by Anonymous Coward · · Score: 0

      Hence the problem. What the linux/Unix world does not get is the word intuitive. There is a lot about GIMP and Linux for that matter that is not inuitive and well plain convaluted. Even if you look at something like paintshop pro versus photoshop there are tools that universally work the same way.

      For some reason many open source apps like GIMP just have to go against that grain and force things to be different just for the matter of trying to be different or supposedly improve on something, and in that, they make things unfamiliar and un-intuitive. You are not going to force the world to work your way. Especially those of you from the green screen world, which is like working your app backwards instead of forwards.

    3. Re:GIMP can't even draw rectangles by ObsessiveMathsFreak · · Score: 1

      Hence the problem. What the linux/Unix world does not get is the word intuitive.

      They get the word, they're just too lasy to code basic MSPaint style tools into the GIMP is all.

      --
      May the Maths Be with you!
    4. Re:GIMP can't even draw rectangles by crimperman · · Score: 1
      Select a rectangular area with the select tool. Click the 'selection to path' button, then the 'draw path' button. Not exactly that direct, I'll agree, but there's no fiddling around with masks required.


      I'll agree it's not intuitive it took me six months of using it before I worked out how to draw a circle/rectangle. That said this is the way I do it..

      Select a rectangle/circle with the select tool. Choose Stroke Path from the Edit menu. Set your brush (if required). Click OK.
    5. Re:GIMP can't even draw rectangles by ylikone · · Score: 1

      Hell, I've "learned" to draw circles and rectangles in Gimp many times now. Each time I need to do it, I forget how, and need to google for it. What kind of application requires you to google search every time you want to draw a basic shape. HA! That is what I call VERY BAD, UNINTUITIVE design. I'm a Linux user, so Gimp is all I have and it's a love/hate relationship.

      --
      Meh.
    6. Re:GIMP can't even draw rectangles by Anonymous Coward · · Score: 0

      Sarcasm?

  117. Sven is a bit of a jerk by Anonymous Coward · · Score: 1, Informative

    Look what he had to say to the GimpShop guy - http://gug.sunsite.dk/forum/?threadid=2721 - heaven forbid somebody try and improve on his oh-so-holy project!

    Yes, it is HIS project, but the second you GPL the code, it's out of your hands and flaming people for trying to do something new with your idea is petty. You aren't by any means required to provide support to the forks (I'm sure he has no love for the FilmGIMP/CinePaint devs either), but a lack of civility makes your own project, nay, OSS at large, look like a giant group of elitist pricks.

  118. Re: Adobe Acrobat on Linux... by Brane2 · · Score: 1
    While Adobe has been edging toward Linux for some time now, it also took its own sweet time in bringing the latest version of Adobe Reader, aka Acrobat, to Linux. After all, Adobe didn't even release Version 6 for Linux.



    How come then, that I have Acrobat 7.0 emerged on my Gentoo for some time now ?

  119. Photoshop sucks. by MikeFM · · Score: 1, Interesting

    Photoshop itself sucks. If you have an equal amount of experience in it and GIMP then most of the time GIMP will be easier to use in my experience. Where Photoshop shines isn't in itself but in all the add-on's that are available for it. If GIMP could make those add-on's work with it then it'd be a killer program but even so for the vast majority of graphic work you don't need all those add-ons to get things done.

    Photoshop is mostly asked for because most graphic arts people have trained on it, and only on it, and lack the ability to adapt. It does have some capabilities Gimp lacks but likewise Gimp has some capabilities Photoshop lacks.

    Of course my opinion may be twisted as I'm the kind of person that thinks a good drawing program should have a command-line option. Still, with no formal graphic arts training, I can produce graphics of equal or better quality as most 'real' graphic artists I've worked with in less time than they take to do the job and I think a lot of that has to do with using Gimp rather than Photoshop and just knowing a lot of tricks to gettings things done. I'm often amazed at how many graphic artists don't really understand how their tools work and therefore don't think of a lot of possible uses and shortcuts. I've found that when you find a graphic artist that has both talent (knowing what looks good) and knows their tools then you better keep hold of them because they aren't easy to replace.

    An oft unmentioned paint program I like but rarely use is Paint Shop Pro. For quick and dirty stuff that isn't overly involved it is really good. I'd rather have it ported to Linux than Photoshop.

    --
    At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  120. That's exactly why it is so easy to copy. by typidemon · · Score: 1

    Phase 1: Let people steal our software

    phase 2: Those people get hired as graphic artist and can only use photoshop

    Phase 3: Profit

  121. Slicing is the main feature the GIMP needs! by kale77in · · Score: 1

    > As powerful as GIMP is...

    There are a few killer designer-friendly features that just don't seem to have enough mindshare amongst developers to make it into GIMP, but slicing is the BIG issue.

    (For the non-designers: Slicing means having multiple subimage exports from the same picture, arranged by green transparent rectangular overlays which snap-to-rules and each have their own export/compression settings. It's graphically analogous to scripting in the sense that it doesn't just make you work faster; you actually work significantly differently once you grasp the possibilities).

    This was where Fireworks took on Photoshop and comprehensively beat it for a few years, partly by the ease of slicing and partly because of its lovely styles/vectors integration. It had all this in 2000 or so.

    I'm hoping Inkscape will adopt a slicing tool, but GIMP has needed one for some time now. The python/perl ruler-based slicing tools are pretty painful once you've used Fireworks, ImageReady or Photoshop.

    1. Re:Slicing is the main feature the GIMP needs! by BigSven · · Score: 1

      You mean something like this, don't you: http://gimp-sharp.sourceforge.net/screenshot-6.jpg

  122. WOW! by Anonymous Coward · · Score: 0

    gimp sucks, film at 11.

  123. Re:Also no native CMYK by zrenneh · · Score: 1

    The GIMP also doesn't have a CMYK colour-space. This is essential for print work: I know plug-ins exist, but this just isn't as friendly as native support: I'm extremely surprised there's no native support for CMYK. In comparison Film GIMP/CinePaint has the RGB colourspace required for film work, and a notable user-base. If CMYK support is added, the GIMP would stand a much better chance against Photoshop.

  124. GIMP is not Photoshop, period by Pecisk · · Score: 3, Insightful

    And it is not replacement for Photoshop, either. But post scriptum: for PROFESIONALS. For other crowd who pirates Photoshop just for little tweaks (who are also just people who takes "first hit for free") GIMP could be good enough.

    See, I said - could be. Yes, GIMP has it's own share of problems and it feels somehow stagnated, sure. It could be better. So it is just too little confusing in GUI and lacks good help mode. That's all.

    For professionals it is completely other story.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    1. Re:GIMP is not Photoshop, period by Anonymous Coward · · Score: 0

      A confusing UI and no help? Well that pretty much defines an unusable application in my book.

    2. Re:GIMP is not Photoshop, period by robertjw · · Score: 1

      a confusing in GUI and lacks good help mode fits my perception of Microsoft Word and plenty of people use that. Gimp's GUI is adequate for basic operations. More advanced work can be confusing. Photoshop isn't the easies app to just pickup and use either, that's why most colleges have classes on it.

    3. Re:GIMP is not Photoshop, period by Creepy · · Score: 1

      I have to agree with you there - for me, the difference between Photoshop and Gimp are huge, tho for the last couple of years I've used Paintshop Pro, which I found a nice package and I prefer it to either for photo editing (yes photoshop is more powerful overall, but everything I use is in PSP and it's much easier to use, IMO). I think Gimp is improving - the UI changes from 1.x to 2.x were necessary, but some stuff like red eye removal are still painful (I prefer the channel select method, in GIMP, but try to teach that to a newbie).

      Oddly enough, I do most of my programming on mac and linux these days, but all of my texture editing in Windows... maybe that's just weird to me because I also own a mac and have photoshop on it, albeit now a very old version - 3.x. I got screwed by Adobe's version-to-next-version only upgrade policy since I had a menial job over 4.x's lifetime and the (specifically the academic to professional) upgrade was no longer available after 5.0's release. I still have limited Photoshop access at work (version 6, not the new one - CS or whatever).

      OTOH, my preference to Photoshop and PSP may be me - I liken this to my wife's dependence on Excel - I installed OpenOffice on her machine but it got kicked off for a full (professional) version of Office a month later because of her dependence on VB Scripting, menu layouts, OLE (or whatever MS calls it now) links into MS-Word docs, and Access database. I'm sure many of the things she does also exist in OpenOffice (she's huge on Pivot tables, which I've done in OO and even exported to Excel), but learning a new tool wasn't worth the time for her, doubly so when she can just get her office to pay for it (for that matter, I can too, but I refuse ;)

  125. GIMP sucks as a user experience by DrXym · · Score: 4, Interesting
    I don't care what uber powerful features it supports. If simple operations can be an exercise in frustration then the UI needs fixing.

    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.

    1. Re:GIMP sucks as a user experience by dennisbj · · Score: 1

      In the development version of gimp when you resize an image you can select in the resize dialog if the layers should be resized or not (and what layers, for example all image sized layers).

      It maybe doesn't happen fast enough for most people here, but things do change to the better.

    2. Re:GIMP sucks as a user experience by gosand · · Score: 1
      First off - love the GIMP. I have never used Photoshop, and use Linux at home and work. GIMP has served me very very well for what I use it for. I have done some things in it that have made Photoshop users say "nice!". (I just do graphics stuff for fun, not my profession at all - anyone with minor talent would kick my butt with Photoshop)

      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?

      This annoys the crap out of me as well. It happens all the time. Then there are things like when I am zooming in on an image, it will mysteriously jump to 1200%. I can't figure this one out. I'll be clicking in (+) and then all of a sudden ... BOOM. I am looking at a massive zoom. Extremely annoying, and I can't figure out why it happens. But it has been doing that since the early versions. And there are many many other examples of things like this. But I live when them, through gritted teeth sometimes, and still enjoy using it. It is an awesome free tool. But I think it needs to get a lot better in these small nuances.

      --

      My beliefs do not require that you agree with them.

  126. Why not links in the article? by houghi · · Score: 4, Informative
    --
    Don't fight for your country, if your country does not fight for you.
  127. It's free-as-in-beer by BenjyD · · Score: 1

    GIMP is zero-cost software, why would anyone expect it to rival a $600 piece of software? I think the Free software community should really tone down the "replace all non-free software" rhetoric a bit (and yes, I am a free software developer). In general, people buy software because the value it gives them is greater than its cost. If Photoshop saves the user a few hours a week over a free alternative, it pays for itself very quickly. And, in general, the commercial alternative will, because they can afford to hire UI designers and product teams.

  128. yawn... society is still not ready by Anonymous Coward · · Score: 0

    well actually i am using computers since ages... pre mouse era you know...

    the photoshop / gimp talks is somewhat funny to me... heres my opinion.

    1. photoshop isnt that widespread in terms of "licensed original versions" its widespread as copies (just like every popular windows application)

    How many licensed versions of latest photoshop vs downloads of latest gimp + distro spreads are we talking about?

    2. photoshop is commercial and thus if you wanna professionally work with it you gotta buy it.

    3. photoshop due to its popularity sets a defacto gui standard

    But the question is if its really better than gimp. For an artist learning a new tool might be time consuming and a problem... but the question is... why did he start to learn photoshop in the first place? Isnt that an "educational Problem"? I remember when i was at university in germany (a shitty one) i was forced to learn visual basic (a non portable, proprietary old and close to useless scripting language that is closed source). Its a political Problem... Professors get sticked money up their ass from companys to teach their students "their tool of choice (you choose what you get paid for...)". Not very scientific, not very "future save" ... just corrupt and politically uncorrect, but thats life.
    Personally i dont think that the photoshop gui is that great in terms of usability... . I even think that gimp reflects more the "old school non computer art tools". The "toolbox" window is pretty much comparable to a palette to me. But theres the question... how many computer artists are also real artists? i dont know. i wish thered be statistics.

    Also the right click context menu provides quick access to nearly every functionality no matter where your mouse is on the picture (efficient).

    If you dont want to learn new tools i think you shouldnt participate in scientific conversations.

    the idea of "everything i can and have is great while everything else sucks" isnt proper argumentation.

    If you artists out there really want a tool that is free and better than every proprietary tools give more feedback to the developers and support your favourite free projects... if it yet cant replace your proprietary tools go report your ideas upstream but dont do the above with a closed mind wanting to have app xyz reimplemented. We dont wanna have a copy of ages old software concepts... we need new fresh concepts and new fresh ideas to create tomorrows state of the art software products.
    You also wont be able to fly tomorrows spaceships if you dont wanna learn ;)

    My personal experience yet with artists is that lots of those i know are pretty much non techies and also non scientific persons nor geeks. Artists need simple software with less buttons and functionality. Maybe gimp is just too much of functionality and the society isnt ready yet for learning a new gui concept.

    an open source developer

    p.s.
    Summary:

    if you dont like the gimp project you got various options

    1. stop whining and spend your money on photoshop
    2. stop whining and submit feature requests that make sense (=! i want photoshop so gimp gotta be like photoshop) or patches upstream to make the tool better
    3. stop whining and write your own photo/paint software

  129. "Upcoming update" of GIMP by Urkki · · Score: 1, Flamebait

    From TFA: 'I wonder if some Photoshop fans just haven't looked at GIMP's upcoming 2.4 update.'

    Gee, I wonder that too... I mean, everybody should just look at upcoming updates of all software they're not using... Stupid Photoshop fans.

  130. A better GUI for Gimp wouldn't hurt by IYagami · · Score: 1

    >A better GUI for Gimp wouldn't hurt
    See GimpSHOP at http://plasticbugs.com/?page_id=294

  131. I can see why by PrayingWolf · · Score: 1

    I use GIMP a lot for producing .eps files for my LaTeX articles and I've often wondered why I can't even draw a line in GIMP. I know its an image manipulation program and therefore it doesn't have to be a drawing program, but I'd really like to find simple things like this in it...

    1. Re:I can see why by Anonymous Coward · · Score: 0

      You can, though it's not exactly as simple as Paint or similar.
      Create Path; draw line on the image.
      Go to the Paths tab in "Layers, Channels, Paths" and right click on it. Select "Stroke Path".
      Select line width, style, brush and suchlike, click Stroke.

      Voila. One line.

      Hope it's useful...

    2. Re:I can see why by minus9 · · Score: 1

      "I've often wondered why I can't even draw a line in GIMP."

      Hold down the shift key and it draws a line.

  132. Lorraborox by ishmaelflood · · Score: 4, Interesting

    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.

  133. Bad .jpg quality with Gimp (on Linux) by cyxxon · · Score: 1

    One thing that always makes me go back to using Photoshop (or even Photoshop Elements) or any other freeware/commercial image manipulation application is the bad image quality I get when saving as .jpg under Linux. I have that under Debian, my girlfriend has that under Ubuntu and had that under FC. Most recently my girlfriend had the same problem with Krita, so maybe it is a problem with the library for this (libjpeg? not that much of a Linux guru).

    And the quality is so bad in that I can easily see this. My girlfriend is an internet erotic model (cue stupid /. jokes about people here not having a girlfriend or whatever), and whenever I see a pic on the internet on her site or Myspace profile and it just looks crappy, I ask who edited it, and then she already looks at me with this "I know, I know, don't fucking ask" look and says she did it, with Gimp, or lately, Krita. When she does the job on my Windows laptop with Photoshop, pics always look great. And no, she is using the best jpg quality (12 or 100% or whatever the setting is called).

    Had anybody else problems with this? I mean, I seriously cannot recommend the Gimp for any photo editing tasks as long as it does not produce top quality images with so simple a task. Are there different versions of the library, because of patents or the like? Is there a hidden switch, like "don't garble the pic with random noise and artifacts"?

    1. Re:Bad .jpg quality with Gimp (on Linux) by polyp2000 · · Score: 1

      Personally i have found the jpg quality of gimp to be fine.
      As always its best to tweak the settings in the dialog to get the best results.
      I always make sure Subsampling is set to "1x1,1x1,1x1" and DCT Method set
      to floating point. Those will single handedly improve the jpg quaity. Then you can adjust
      other sliders and checkboxes together with the preview function to get the best results.

      Nick ...

      --
      Electronic Music Made Using Linux http://soundcloud.com/polyp
    2. Re:Bad .jpg quality with Gimp (on Linux) by trollable · · Score: 1

      Do you have any picture so I can judge the quality of this JPEG encoder? (joking)

      That said, I noticed it too but the quality can be fixed. At 95, it is in general fine. At 90, it is acceptable. But that depends on the size and type of pictures. That would be interesting to have a fair comparaison with other libs.

    3. Re:Bad .jpg quality with Gimp (on Linux) by Duckx · · Score: 1

      JPEG encoding is always a touchy subject. Even PS IMHO is a bit under. I always end up having to save as PNG/TIFF and do the final encoding in PhotoImpact, because of better options/quality. And no, "Save for Web..." just won't cut it. Its always mind bending to watch the JPEG encoder ruin all your carefully crafted unsharp masking...

  134. Resizing selections... by Anonymous Coward · · Score: 0

    Hell, just easily resizing selections should save more than that. Whoever said that adding and subtracting - without even constraining anything - was good enough should be shot. No, drawn and quartered. And hanged. And then shot.

    You have to be able to drag the borders!

  135. Bwhahahaha by Anonymous Coward · · Score: 0
    The GIMP developers will be happy to hold your hand and answer your questions.

    Bwahahahahahahahahaha! Hahahahahahaaaaaaahhaaahahahaa! You mean.. ahahahahahaha oh wait... hahahahahahahahahahahahaha!

    Man that was hahahahaha, great, hahahaha. *Wipes tears*

    Best laugh I had in weeks. Thanks!

    ---

    (as you can see, I've been to your list, I've asked if I could help. Hi Carol, Sven!)
    1. Re:Bwhahahaha by BigSven · · Score: 1

      No, I can't see this. You are an anonymous coward and obviously trolling.

    2. Re:Bwhahahaha by beaviz · · Score: 1

      (i didn't post the original, but i'll respond)

      I have actually done a patch for the Gimp (Rewrote the Hue-saturation tool for more speed and correctness). I use it daily and a few of my friends do. But it's not in Gimp, why?

      When i first developed it, i joined the developers irc-channel. That was a rude awakening.

      I presented my patch with an example webpage demonstrating the differences. The following happened:

      - Some people saw interest and was generally pleased with the speed and result (that includes you i believe).
      - Some people helped me place my helper functions in the right places.
      - Many people told me: "Stop doing that, it's useless, we're moving to GEGL".
      - Some people complained that a hadn't talked to anyone beforehand.

      I received a LOT of stop-energy. It was a really bad experience aften i had used 50+ hours making the patch. I simply gave up. Sorry.

  136. Fine, since you asked: here's why GIMP's GUI sucks by KWTm · · Score: 1
    Ah. You asked. Here's your answer, at least partially.
    1. CURSOR SHAPE DIFFERENT FROM TOOLBAR ICON

      The way the toolbar icons are not the same as the cursor icons. For example, the crop/resize tool button in the main GIMP window looks like a paintbrush, but a different sort of paintbrush from the real paintbrush. (Later I theorized that the icon actually represents an artist's knife, for the "cropping" part, although I don't know how that relates to "resize".) But when you move the cursor onto the sheet, the "crop&resize" cursor looks completely different, and I'm not sure I've selected the right function. I'll let you find other examples of where the cursor shape is different from the toolbar button.
    2. MASK

      The way the "mask" concept is implemented is non-intuitive. You have a selected area, and anything you do only affects that selected area. For example, say you select a rectangular area in an empty layer. You fill the layer with a certain colour (using the Pouring Paint Can tool), expecting the entire layer to get filled, but only that rectangular area gets filled, even if you clicked the Pouring Paint Can outside the selected rectangle. All well and good, but ...

      Suppose the mask is so small that you can't see it, or you don't notice that you have a mask on because you've zoomed to another area? Especially since I can't seem to find how to get rid of the mask. Say I used the mask for some other operation, eg. touching up the picture somewhere else. Now I want to get rid of the mask and operate on the entire drawing.

      You could say, "Well, there's a keyboard shortcut for turning off the mask. It's [whatever]." Well, again, since GIMP is a GRAPHICS manipulator, I would expect something in the GRAPHICS user interface.

      You could say, "Well, you can select the entire area." That's a cop-out.

      The real question is, how am I supposed to know that there is a mask in the first place? I tried to get rid of the mask by using the rectangle selection tool and double-clicking in the picture, effectively making a mask of size 0. Well, GIMP thought that I actually did want a mask of size 0, and from then on none of the drawing tools worked (because they only operate on what's within the mask, and the mask is size zero). If I had not remembered that I had set a 0-size mask, I would have thought GIMP was not working.

      There should be some indicator in the status bar that the mask is on. When the user double-clicks the selection tools (the dotted rectangle, dotted circle, or lasso), there should be a pop-up window with various options including "turn off mask".

      (By the way, for anyone trying to tell me "but Photoshop does the same thing!" --stop trying to compare GIMP with Photoshop. GIMP should stand on its own, and actually I don't use Photoshop, so that doesn't help.)
    3. STATUS INDICATORS

      This leads to the next topic: status indicators. As we mentioned, status indicators for whether a mask is in effect are sadly lacking. Other non-intuitive problems, where nothing you do seems to affect the picture, can be caused by selecting a non-visible layer: suppose not all layers are visible, and you somehow accidentally select a non-visible layer to work on. You might want to doodle all over your drawing, but nothing seems to happen! In the meanwhile, you are actually defacing a different layer of your drawing without realizing it. This is because the layer status window is a separate window.

      Others have debated the wisdom of using multiple separate windows rather one big window containing all subwindows, so I won't rehash it here. My peeve is that there is only one window for layer status no matter how many drawings you are working on. Suppose you open a 3-layer drawing to work on; you see that drawing, plus the layer status window, plus the main GIMP window (plus the toolbar selection window if applicable). Now open another 2-layer drawing, say. Well, you still have the same window
    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  137. Not entirely fair by HangingChad · · Score: 1
    Maybe this is because GIMP has one of the most god-awful GUIs known to man.

    That's not entirely fair, though I will grant you the interface has been a work in progress. I've found the GIMP is just different. It takes a while to get used to if you're coming from a Photoshop background.

    Over the months and years I've been using the GIMP for things and now I have to stop and think about how to do the same functions in Photoshop. And there are still things in Photoshop I like better. The four-up view for saving an image for the web. Very nice. If GIMP has a similar feature I'm not familiar with it.

    I'll keep using the GIMP, although sometimes I wish they'd change the name. GIMP gives me Pulp Fiction flashbacks.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  138. Why they don't like GIMP by Crouty · · Score: 1
    There are 2 reasons why people do not like GIMP:
    1. Proffessinal designers who need CMYK.
    2. They are accustomed to Photoshop and do not want to start over learning how things work in GIMP.

    Very few users belong to the first group and I (and Adobe as well) suspect that many do not use a licensed version of Photoshop. If they had to pay for one, many of them would be happy to use such a fine program like GIMP.

    --
    On se Internetz nobody noes your German.
  139. Not Slashdot, Slackware by Ilgaz · · Score: 1

    Sorry for typo, it is Slackware, there is no "Slashdot" linux :)

    Allthough, I always counted Slackware as "Slashdot" linux :)

    1. Re:Not Slashdot, Slackware by ConceptJunkie · · Score: 1

      Sorry for typo, it is Slackware, there is no "Slashdot" linux :)

      I hear ./ Linux 1.0 beta 1 (code name "Frost Pist" is coming soon).

      --
      You are in a maze of twisty little passages, all alike.
  140. Krita is better alternative to Adobe Photoshop by billybob2 · · Score: 5, Interesting

    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.

  141. Agree and Disagree by SphericalCrusher · · Score: 2, Insightful

    To an extent, I would agree that GIMP is not enough to make a business convert from Windows to Linux. Windows offers both Photoshop and Paintshop Pro, two extremely great imaging programs and in my strongest opinion, GIMP cannot even compare to those two. But on the other hand, GIMP should be considered a factor in changing operating systems. But let's not forget about the thousands of other exclusive programs found only for Linux... even though more and more are moving away as we speak. For me, I am just happy enough installing the newest version of Cedega and emulating anything I need from every other platform just to keep my Penguin happy.

    --
    "Instant gratification takes too long." - Carrie Fisher
  142. Maybe for some people it isn't enough... by martinultima · · Score: 2, Insightful

    but in my humble opinion, I'd say that the GIMP is the best thing since sliced bread. I just can't imagine working on a machine without that amazing program installed – it's done everything I could ever need it to, whether I'm color-correcting a scanned photo, digitally coloring the likes of Erlkönig, or creating proof that J. K. Rowling's been hard at work on the eighth book that everyone knows is coming. In fact, believe it or not, I've never even used PhotoShop in my entire life; all the graphics on my homepage (except the ones taken from elsewhere, of course, like the background image) were created using the GIMP. And, of course, a bit of ImageMagick here and there; I doubt PhotoShop's going to have a handy command line any time soon!

    --
    Creative misinterpretation is your friend.
  143. I just refuted this article's mistakes yesterday: by Hosiah · · Score: 2, Insightful
    Right here.

    Once again: Photoshop ported to GNU/Linux/BSD/etc=good thing. I'm all in favor of it. Then we can all get off the Gimp's back. I've been fighting ignorance about the Gimp for five years, and I'm sick of it. The reasons cited in this article amount to "We need something else for transportation, because cars do not come with steering wheels, tires, and motors." OK, whatever the reason for the insanity, y'all do what you have to.

  144. Re:Fine, since you asked: here's why GIMP's GUI su by BigSven · · Score: 1

    You have a lot of valid points here. I just hope you realize how pointless it is to post such user interface criticism on slashdot. It would be a lot more helpful to file bug reports for them or bring them up on the gimp mailing-list or in the GIMP forum at openusability.org.

  145. CMYK by McAlt+0178 · · Score: 1
    CMYK mode

    /Thanks to ImageShack for Free Image Hosting

  146. It's been on *nix - you just have to pay (a lot) by dbIII · · Score: 1
    McDonald Douglas ...

    Of course not, they use "Aircraftcad"

    Youngsters may not have heard of McDonald-Douglas CAD - which is what universities lusted after when they could only afford AutoCAD. Today there is IDEAS, ABAQUS, MARK, MENTOR GRAPHICS (capitals are all theirs in the product names) and other things I can't remember, several of which have never has a Microsoft OS version because they require too much processing power for it to have been worth porting. Some finite element analysis packages like ABAQUS have a Microsoft OS version.
  147. enough for me by Apreche · · Score: 1

    GIMP is enough for me, but I barely do image editing. I mostly just crop and resize photos and make simple images for web sites.

    --
    The GeekNights podcast is going strong. Listen!
  148. Listen To People, Don't Ridicule Them by reallocate · · Score: 1

    You're remark is a perfect example of why Linux remains a cult: Linux is for True Believers who'd rather deprive themsevles of access to good tools rather than soil their hard drives with "evil" code.

    Understand that the vast majority of users will not move to a new OS if the programs they use are not available for the platform. Not equivalent programs, not clones, but the identical program.

    Frankly, surveys like this simply confirm the obvious. Gimp has been around, for free, for several years. If Gimp was compelling enough for Photoshop users to switch to Linux to use it, they would have done so. The fact that they haven't -- that they'd rather pay hundreds of dollars for Photoshop and the other Adobe tools than pay nothing for Gimp and Linux -- ought to tell you something.

    Rather than adopting an unwarranted elitist attitude about non-Linux users, you'd be better off listening to people explain why they won't use it.

    --
    -- Slashdot: When Public Access TV Says "No"
  149. A better title for this thread... by QuietLagoon · · Score: 1

    Windows not enough for Photoshop users?

  150. White Balance by Burz · · Score: 1

    Well its good that you found a tool to do white balance, because GIMP sure ain't gonna do it properly.

    1. Re:White Balance by RDW · · Score: 1

      It doesn't have to. Just like with Photoshop, a plugin handles white balance adjustment at the time of raw conversion. For Photoshop, the plugin is Adobe Camera Raw. For GIMP, it's UFRaw or one of the other interactive dcraw-based packages like RougePhoto or RawPhoto:

      http://ufraw.sourceforge.net/
      http://pages.quicksilver.net.nz/pepe/d70/Nikon_D70 _on_Linux.html
      http://ptj.rozeta.com.pl/Soft/RawPhoto

    2. Re:White Balance by Burz · · Score: 1

      And what about images I've scanned in, or downloaded from a friend?

      Um, isn't the white balance in the wrong place??

    3. Re:White Balance by RDW · · Score: 1

      When AaronW mentioned white balance, he was specifically talking about raw conversion (Bibble is also a raw converter, as is Camera Raw, the Adobe plugin that has white balance control). This is the only stage when you have the 'uncooked' data available to adjust the white balance directly (which ought to give you the highest quality output and is easier than messing with the colour balance later on). Of course both Photoshop and GIMP have other tools (channel mixer, curves, levels, etc.) that can change the colour balance in an already processed image like a tiff or a jpeg. In this context, GIMP's main limitations are its lack of support for colour management (finally available in the developmental versions in a limited form) and for 16 bits per channel (don't hold your breath for this one!).

  151. Post Shows Blatant Linux Elitism At Work by reallocate · · Score: 1

    >>"...It's due to the failing of our society to educate people enough to actually understand the tools they work with..."

    That post is a blatant example of unwarranted Linux elitism at work. Why aren't most people using Linux? Because they are clever enough. Therefore, it must be true that people who use Linux are rather more clever than eveeryone else.

    Sure.

    The reason people don't use Linux is because they don't want to use Linux and they don't neeed to use Linux. You don't need to be more clever or smarter than average to use Linux. You just need to want to use it. People who aren't willing to go to the trouble of learning how to program to do something they already do on another platform are simply making a rational choice about how to spend their time and energy. Why learn Perl, for example, to accomplish a task when you already accomplish that task just fine on Windows or on OS X?

    It is egotism that feeds that kind of post.

    --
    -- Slashdot: When Public Access TV Says "No"
  152. Another comparsion to illustrate by Qbertino · · Score: 1

    Ok, so by now we all know PS and Gimp fanboys alike, that PS has features that Gimp hasn't and makes working with images in a certain way possible were Gimp doesn't. Gimp doesn't have protocol, Gimp filters are a joke compared to PS, Gimp layers are ok but again PS excels here. And lets not get started on effects. Corel PhotoPaint is somewhere in between (I'd say closer to PS) and does nearly everything one needs perfectly on linux.
    As I am a professional user that's used all three on professional projects let me provide the bottom line here:
    Gimp -> nice usefull tool for editing images
    Corel PhotoPaint (also available for Linux, free (beer)) -> nice professional tool for editing images
    PS -> the bar

    Even though a lot of stuff can be done with Gimp and might not technically justify buying a licence for Corel Draw/PhotoPaint for Linux (I did this before PP was availlable for free), there is a very good reason to do this anyway. Let me illustrate with another example:

    I'm a Blender Fanboy. Blender rocks. I'm one of the few that own a commercial licence - back from the time where there was a commercial version available for about a year. Blender has come a long way since I joined at 1.8. 3D software vendors are doing wee-wee all over their pants when they see the growing featureset of Blender. It's allready got stuff that no other package in the industry has (i.e. B-Bones). With the ongoing Orange Project features are getting added every other week. I love the programm and I love to use it.
    Yet I still bought a (reduced) commercial edition of Lightwave less than a year ago.
    How's that work out?
    Type in the word "Lightwave" at amazon.com and you'll get one reason. Lightwave has been in the industry for 10 years and it shows. You can get clobberd with books on LW. LW covers workflow from a to z. While workspacemanagement lacks compared to Blender, it is well though out. The Workflow has less to none of the little quirks that can spoil the Blender experience a little. Rigid and softbody stuff is well established in LW and cloth is void of that experimental prototype feeling it has with Blender. Platonic Primitives is a bonus over current Blender (2.4) I just got to enjoy the other day. I could go on but this outlines the issue at hand.
    All in all, for a professional, it justifies the expense of 500 Euros for LW over Blender to get the job done quicker or make that needed extra possible. I have to spend some money on Books, but the point is that they are available. The ones for Blender still have to be written. I've volunteered for that but mind you, writing end user documentation for a 3D package is a hell of a job.

    This is the narrowing difference between established software (be it commercial closed source or not) and software that isn't quite there yet. And believe me, as far as competitive oss design software goes, nothing is as mature as Blender.

    In a way a Gimp/PP/PS debate is pointless. One about Blender/LW would actually be interessting.

    --
    We suffer more in our imagination than in reality. - Seneca
  153. not good enough for WINDOWS users by caffeination · · Score: 1

    Sorry I'm a little late to the barbecue. I couldn't find this point made yet.
    It was a survey of non linux users, for fuck's sake. I'm 90% convinced that the title is as it is solely to inflame. The comments here generally state that it is in fact good enough for linux users, which may be accurate, but only relevant in the context of this STUPID MISLEADING TITLE which has nothing to do with anything.

  154. Gimp is powerful and horrible. by xutopia · · Score: 1

    I'm an avid Open Source Software fan. I distribute linux cds for free at work, to friends and neighboors. I also install Firefox and Open Office to show friends how nice those packages work. The Gimp? No way in hell will I confuse anyone I love with it. I'm sad to see such a nicely programmed application suffer so much from a delusionary view that the interface they have is the right one. So far they don't want to fix it and to me that represents the biggest hurdle for OSS to reach more people. The Gimp being so frustrating is the reason I still use Photoshop.

  155. 16bpp voodoo, show me specs. by twitter · · Score: 2, Insightful
    When people spend big bucks on good cameras they probably know what they are doing.

    They are mostly spending big bucks. 24 bpp + alpha is more than my eyes can discern and I'd be surprised if the other 24 bpp was not mostly white noise to the camera as well. It's hard for me to imagine light and voltage differences controlled so finely in the imaging or display devices. At 16 bits you are talking about 65,536 levels of difference on each pixel. At a generous 5 volts, you are looking at controlling your signal to 7.6E-5 volts. If either your fancy camera or monitor can control line ripple to 1E-4 V, I'll give you a nickel of your money back.

    As a test, take a picture of an object that's supposed to be one color under the most uniform lighting you can make then tell me how consistent all 48 bits of your color space are. I'm really interested. Point me to specs if they exist.

    --

    Friends don't help friends install M$ junk.

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

  156. gimp vs. photoshop by kcornwell · · Score: 1

    a bit off topic but... As a noob to both gimp and photoshop and I must say gimp is more intuitive to me. Some of the guys in our IT dept are now using it as well. :)

  157. I'm a zealot! by ylikone · · Score: 1

    I'm a Linux and open-source zealot. I love that the Gimp exists and it is a powerful product... BUT I admit that it needs a lot of work on the GUI. Maybe the people that made it and maintain it, like it... but NOBODY ELSE DOES! This is NOT a generalization. The GUI really stinks, even with all the improvement they've made to it over the years! I don't see why Gimp hasn't had a successfull (meaning popular, yes I know about cinepaint or filmgimp or whatever, hardly popular and not a better GUI anyway) fork yet with a completely redesigned GUI.

    --
    Meh.
  158. What about for non-professionals? by walterbyrd · · Score: 1

    I am a casual user of image manipulating software. I have never used photoshop. I use gimp, and I use those give-away apps that come with my scanner.

    From my experience, gimp doesn't work as well as the give-aways. For example, using gimp, I cut a section out of a 3.5MB jpg. Gimp warned me that I need 225MB of RAM to store the section. I went to past the section, and was warned that gimp needed 335MB to paste the section. Gimp was also going *very* slow.

    I rebooted into windows, and used some give-away software to complete the process easily, and quickly.

  159. a few more... by ylikone · · Score: 0
    3. The GUI impedes getting real work done.. as it is not properly laid out (read some of the MANY posts before yours for detailed examples)
    4. The name sucks and is innappropriate for a business setting. Why the hell did they name a product "The Gimp"?! That is just utterly stupid and offensive. I mean, come on, use some common sense and rename it already!

    On a different note, I am planning a new distribution of Linux called "Crack Whore Linux©". It will be awesome and powerful... why would people not use it?

    --
    Meh.
    1. Re:a few more... by Crouty · · Score: 1
      Ack. I do hate the file dialog of GIMP under Windows.

      The name may be stupid but I sure don't feel offended by it and don't care if someone does not use GIMP because he judges the book by its cover. But I agree, naming is important if you want as many users as possible.

      --
      On se Internetz nobody noes your German.
  160. Sorely missing by ylikone · · Score: 2, Insightful
    Yes, I fully agree with you. Although I don't use my Windows machine much... easy image manipulation is much easier with it using the give-away software. I hardly ever work on graphics, except for your basic needs, resize, crop, red-eye fix, color or brightness enhancement, etc... These are not simple one-click things to do in the Gimp. Even when I have learned the methods of how to do things like red-eye reduction in the Gimp, it seems like a stupid and hackish method, with not always desirable results. In ANY give-away windows photo manipulation product there is a simple option "Reduce red-eye" and you click it and it just works. Why doesn't Gimp have something as simple as this built in? For that matter, why is there no open-source image manipulator that has this built in? (at least none that I can find)

    There really is a need for a simple image manipulator for the masses with just the basic photo editing functions available in a single-click. I wish I knew how to code C++, I would program it myself.

    --
    Meh.
    1. Re:Sorely missing by ninja_assault_kitten · · Score: 1

      So is nearly every piece of software X11 supports. X11 is holding Linux back.

    2. Re:Sorely missing by ylikone · · Score: 1

      I hate to reply to my own post, but I did fail to mention "DigiKam", which is almost exactly what I would want in simple photo editing software... as it has "red-eye reduction" as a menu item, as well as some other basic tools. The problem with it (apart from being a QT/KDE app) is that you can't just load and edit a single image directly with it. You have to "import" and image into your album, then "export" it back. Stupid. If anybody know of a GTK equivalent to DigiKam that allows direct access to individual image files, please post here and tell me!

      --
      Meh.
  161. Watch GIMP Suck Eggs with the Stroke Tool... by httpamphibio.us · · Score: 2, Interesting

    Simple test... create a new image, use the ellipse select tool to create a circle, stroke that circle. Look how absolutely nasty and NOT SMOOTH the stroke is. If GIMP can't handle a simple operation like stroke how on earth is it supposed to make people think it can compete with Photoshop?

    --
    sig.
    1. Re:Watch GIMP Suck Eggs with the Stroke Tool... by Ford+Prefect · · Score: 1

      Simple test... create a new image, use the ellipse select tool to create a circle, stroke that circle. Look how absolutely nasty and NOT SMOOTH the stroke is.

      Work-around: use the ellipse select tool to create a circle, Menu: Select: To Path, clear the selection then Menu: Edit: Stroke Path. Beautifully smooth, plus it's kept the path so you can edit with the bezier tool and whatnot - have a look in the Paths tab of the Layers dialogue box.

      --
      Tedious Bloggy Stuff - hooray?
  162. Photoshop for UNIX by Kadin2048 · · Score: 2, Informative

    I brought this up last week in a different discussion, but not only did they have a version for SGI at one point, they had a version for "UNIX" in the form of SunOS/SPARC. It was for SunOS 2.x and I think it was around Photoshop 3 or so.

    This place has a PDF version of the Adobe product brochure:
    http://computing.ee.ethz.ch/sepp/photoshop-3.0.1-s t/photoshopSun.pdf

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  163. Re:How can we take this seriously; book needed by Anonymous Coward · · Score: 0

    Judging from your experience, it sounds like a Photoshop to GIMP handbook would be very useful and potentially a big seller.

  164. plugins! by TheGratefulNet · · Score: 1

    I am a long long term linux and freebsd user (since about '94). I use unix for my software devel work and I run a freebsd server at home for web/dns/ssh/mail and so on. I have been using unix since the mid 80's.

    I hate MS and windows. I hate XP.

    but I use pshop cs2. why? it actually works and for my photo hobby, it delivers.

    HDR (high dyn range) processing for stacking bracketed images. gimp doesn't have this, I don't think.

    16 bit color channels. I need this for raw processing.

    neatimage (noise reduction plugin) does not run on gimp. they say the standalone version runs on wine but that's a poor 2nd to a native binary and plugin. I NEED NEATIMAGE (my camera is noisy and it can't be helped). neatimage was well worth the $50 I paid for it but it does not exist on unix ;(

    video is slow on unix compared to windows. all the x11 layers you have to go thru vs 'video in the kernel' of xp. this feature makes windows less stable - BUT it also makes bit blitting and video updates so much faster. (in fact, I use xp as my vnc-viewer system and my bsd box is my vnc-server. vnc-viewer on windows is MUCH faster than tightvnc or realvnc on unix. sadly to say...)

    if the plugins will run on gimp AND the UI becomes closer to what us photogs are used to - AND all the other issues, above, are addressed, then I'll move back.

    --

    --
    "It is now safe to switch off your computer."
  165. complaining about free things by reaktor · · Score: 0

    If something is free, people complain. I'm sure if GIMP had full time paid programmers, it would indeed surpass Photoshop. Hard to compare free/unfunded vs. the corporate world. Instead of complaining, I'm sure the GIMP team would take a financial contribution or your own programming skills to make it better.

  166. Simple solution here.... by plazman30 · · Score: 1

    And that would be to continue to develop GnuSTEP and make is as API compatible with Cocoa as possible. Now, I know that Photoshop is an Carbon app, and therefore would not port to GnuSTEP, but there are plenty of other applications for OS X that are Cocoa and WOULD port to GunSTEP with some minor recompiling.

  167. I know at least one by Anonymous Coward · · Score: 0

    My sister is tired of Windows breaking on her, and can't afford a brand-new Mac. She'd switch to Linux in a heartbeat, but she's an art major and needs her Photoshop. It's not that she couldn't learn GIMP, it's that she already made the investment of time and money into Photoshop, and she's got little of either at this point.

  168. What Linux Really need is ..... by Anonymous Coward · · Score: 0

    ... more text editors, mp3 players and photo album organisers. The people surveyed have got it all wrong!

  169. The creative process isn't as creative on Linux by woolskit · · Score: 1

    I'd like to weigh in as an Artist/Coder. I think maybe I can shed some light to the GIMP/PS debate given my experience with both sides of the divide (creative/artist versus coder/hacker).

    I do web design as my primary job, but I'm also doing freelance print design, web development, photography, illustration and video. I use almost all of the Adobe products (and formerly Macromedia ;) I have also been dabbling with Linux since Red Hat 5 and been using the GIMP since before version 1.

    I deeply respect the OSS community and believe in it, support it with Creative Commons and use the tools it provides. I want to use Linux and hate that I'm forced to use Windows: I would switch to Linux in a second, if it did what I need my computer to do.

    What do I need my computer to do? I need my computer to not get in the way of my creativity. Period.

    I've installed many distros of Linux, and setup "equivelant" installations to my Windows box, but when it comes down to doing what I do (being a creative digital person) I can't create without recompiling some code, (re)searching through hundreds of webpages to figure out what OSS app will do something close to After Effects (or even Photoshop), or just running into wierd GUI setups that aren't intuitive enough to me. When I'm creating, I don't want to stop in the middle of it to decipher how a tool works (or hack it if it doesn't work). I just want to keep drawing/recording/editing/playing.

    I know how to program, I know how to open the box and fix everything. I can do what i need to do. But as a creative, this is too much of a hindrance. As soon as the creative flow stops, that's it. Adobe's products keep me moving and focused on my work instead of how to do my work. This is the single most annoying thing about Linux for me.

    I'm at the point now where I don't have time to spend a whole weekend installling a system and tweaking its settings. I just want to make stuff. Adobe + Windows allows me to do this. If Adobe could just support Linux for its apps, I'd convert right away. Sure GIMP is a good equivalent to Photoshop, but any creative person using a computer isn't only using PS for all their work you know. Where's the equivalent of Illustrator, or inDesign, or After Effects, or Premiere, or Flash? (I know of the Linux equivalents, but that doesn't mean they're actually equivalent).

    As a person I want to use Linux. As a multimedia artist, I can't. Adobe + Linux would be a dream.

    What do we do next?

    --
    Robert McLarty Multimedia Designer
  170. Apparently you're not smart enough by bradleyland · · Score: 1

    "Most folks aren't smart enough to realize that if they switched to Linux, they wouldn't have to pay for upgrades. However, more importantly, they don't realize that they could hold onto their machines a while longer because the newer versions of Linux rarely push you off of your current hardware onto the latest and greatest."

    And apparently you're not smart enough to realize that computer hardware is much, much cheaper than man hours.

    Knowledge worker salary: $27k-$45k per year
    Brand new computer: $1200

    Take the median of those incomes, $36k/year, and look at what percentage a new computer upgrade costs. It works out to around 3%.

    And about the 10 year old hardware. Give me a break. We'll benchmark your 10 year old GIMP workstation against my pretty basic Athlon XP-M 2500 workstation and see what the percentage improvment is. Now, apply that to worker man hours and the math will definitely come out in my favor. Being cheap can be a detriment. Recognizing when it makes sense to upgrade to new hardware is a business decision, not a geek decision.

    Basically what you get into is a TCO argument. We all know that there are two camps, but to say one camp is not "smart enough to realize" just because they won't yeild to the other's view, is an incredible display of hubris.

    1. Re:Apparently you're not smart enough by eno2001 · · Score: 2

      I'd gladly accept that challenge. I'm pretty certain my Dual PII 300 with 768 Megs of RAM would be only slightly slower than your workstation. Chances are there would be maybe 20-30 second differences in most math intensive filters. I've got a P4 workstation as well and it doesn't do much better than the old dual P II...

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  171. So make GIMP work like photoshop by Ginger+Unicorn · · Score: 1
    Why doesnt someone just alter the UI on GIMP to mimic Photoshop as closely as possible?

    I imagine implementing an MDI would be a bit of work but simply rearranging the menus must be trivial. As far as I can tell from my dabbling with GIMP, the logic of its functionality mirrors Photoshop pretty closely, but the menus are in slightly different places. (it took me ages to work out where "auto levels" was).

    It's irritating that UI preferences cause so much reluctance to make a potentially beneficial switch to FOSS but it's just human nature.

    Desktop GNU/Linux adoption is happening so slowly because there is little pressure on FOSS developers to address the genuine criteria by which casual computer users evaluate their experience.

    For instance McDonalds don't sell millions of burgers because they are lovingly prepared and full of nutrition. They know perfectly well what motivates people to purchase and consume food, so they invest massively in these areas (make the food addictive by packing it with salt, sugar and fat, flood the public conciousness with advertising associating your food with health, sex and happiness).

    Likewise Microsoft didn't sell millions of copies of windows and office by crafting lean, robust and open code. The pump it full of features to give the public a reason to keep upgrading, and sacrificed security to make it easier to use for non-techies.

    While it seems fairly certain to me that you have to cater for this public stupidity(*) in order to shift volumes of product, i think that the FOSS community has the opportunity to do this without exploiting that public stupidity, or undermining the idealistic goals underpinning the FOSS movement.

    (*) i dont mean this condescendingly - i'm referring to the general human capacity for stupidity that everyone has, including me ;-)

    Without the financial imperative that Microsoft or McDonalds are totally dominated by, FOSS could provide the best of both worlds: stable, open, comprehensively featured, freely available software, that is also appealing on a superficial, casual level.

    "Casual user" considerations can often require as much effort as the rest of the project, and as such aren't a particularly appealing expenditure of resources for a developer who is mostly concerned with producing powerful and robust software.

    But as Microsoft and McDonalds have demonstrated, it is perceived value that counts in the public conciousness. In much the same way that the taste of Big Mac holds more weight than the fact it is poisonous filth, the horrific security and questionable licensing of Windows is disregarded because it takes less effort to understand how it works.

    I think that commercial pressure on companies such as Red Hat, Linspire, etc will provide the pressure needed to expend sufficient resources on perceived value.

    The great thing is, with the FOSS system, there doesnt need to be any trade-off. The incredible efficiency of open reusable code means the FOSS community now has the opportunity to create the software equivalent of a healthy Big Mac.

    --
    (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
  172. Damnit! by ylikone · · Score: 1

    I looked a bit further into DigiKam.. and realized there is also Showfoto, which is exactly what I'm looking for. Heck, I've been using Linux this long and didn't know about Showfoto, I feel like an idiot!

    --
    Meh.
  173. Photogenics by Anonymous Coward · · Score: 0

    What something on Linux that is better than GIMP & Photoshop? Photogenics is the ticket!

    http://www.idruna.com/products.html

  174. Crop in the GIMP by tjwhaynes · · Score: 1
    I am a normal user and not a graphic designer. Thus, I do not use complicated features in Photoshop or GIMP, just the low level features. One of these, however, is crop. And crop sucks on GIMP. With Photoshop it is simple, I put a box around what I want to crop to and I crop. With GIMP there are three crops, none of which are very good.

    Err? Okay - try this in the GIMP.

    1. Shift-C (or click on the Crop tool in the button box - it looks like a knife).
    2. Drag a box over the image - this should darken the unselected stuff to make it obvious what you are keeping.
    3. Click on the Crop button

    I fail to see what is causing you problems.

    Cheers,
    Toby Haynes

    --
    Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
  175. Wine runs photoshop right? by paperclip2003 · · Score: 2, Informative

    I am sure 20 slashdot users will say STFU troll but doesn't Wine http://www.winehq.org/ run photoshop? I have been using wine a lot lately and most programs that I don't have windows versions for started really running well with current wine versions 9.5+. I have not tried photoshop in wine, but I would be really suprised if it did not run.

  176. The OSS Community is Not That Simple by poofyhairguy82 · · Score: 2, Insightful
    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 people 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.

    The essential problem is not a problem with the OSS community. Its a problem with the fact that the OSS community is so diverse that it is not possible to label it in a way that does not avoid contradictions. One such contradiction you pointed out is the simple one that many OSS projects are not friendly enough to pull in converts yet many in the OSS community want everyone to convert from closed source software. But this falls apart when you don't try to apply a label to THE ENTIRE OSS COMMUNITY as a whole and focus on what each faction within the OSS community wants. And that sucks, because human nature prefers simple labels for everything.

    What do I mean by that? Simple- some factions of the OSS community care about certain things more than other factions do. For example, maybe those in the GIMP community couldn't give a damn about converting another single user from Photoshop. Who could blame them- for years they have been assaulted by those demanding that GIMP do "this thing" or "this feature" exactly like Photoshop does. So maybe they don't care about spreading OSS to the professional crowd. I can tell you after a year of using desktop Linux I no longer push it with others like I normally would because I am sick of hearing people gripe about not getting their games to play like they want. This can also apply to other parts of life- my father quit offering a cosmetic procedure in his private medical practice just because he was tired of hearing people gripe about the side effects he told people they would have before he did anything. Sometime you get sick of complaining.

    Yet those in another OSS group the goals might be very different. Those people supporting Firefox for example probably DO want to switch over most of the world because the higher marketshare Firefox has the less chance web designers will make pages that work only with IE. They obviously care because that group has things like "Spread Firefox" combined with an emphasis on marketing (full page Firefox ad in NYT). So for these people the gripes of ex-IE users matters a lot more.

    The biggest problem with OSS community is that you can't tie together the GIMP people and the Firefox people and the Ubuntu people with a common label. EACH OSS COMMUNITY has its own priorities...each has its own wants and needs. This is a very bad situation for those of us who DEMAND simple labels for everything, and who are used to a software industry that DOES have a common label and purpose (to please customers to make money). What is even worse is when some takes this traditional perspective on software development ("you are doing this for me the user and no other reason") to the OSS communities and finds that a particular community could not give a damn about its potential "customers."

    Some look to the OSS community and do not see the factions and believe the community has many contradictions. It doesn't. Its more complicated than that. Yes that sucks for many people who demand simplicity, and it is part of the reason OSS fans backlash against the "morons" that do not understand them or their cause.

  177. Seriously, One of the Reasons I love GIMP... by sweetnjguy29 · · Score: 1

    ...is that if you install GhostScript and change some environment variables, you can manipulate any pdf file! No need to spend 100s of dollars on Acrobat to fill in pdf files! Unfortunately, you have to save them as bmp files instead...but you could drag the bmp into openoffice...and then export it again....

  178. It's Not Enough by Anonymous Coward · · Score: 0

    The points brought up in the article are nothing new. I've seen the same thing for *years*. The real problem is that I don't think the open source crowd really believes there are different classes of users.

    Take a related case-- Microsoft Office. To many in the open source crowd, they look at things like StarOffice and so on and say, "see, we have exactly the same thing." No, you don't. You have exactly the same thing for casual users. The user who wants a spreadsheet to add a column of numbers and get a quick graph. The user who types a letter to Mom in a word processor. The user who wants a quick database. All these users are well served by what the open source community offers. And yes, that's probably the majority of users.

    But it's not all. What many people in the open source world don't seem to get is that there are professional users with higher expectations. They don't see Excel as a spreadsheet, they see it as a platform where third-party data analysis add-ons are used. They don't see Word as a word processor, but a reporting component in a larger system. They don't do simple data analysis with Access, they are constructing huge databases with sophisticated relational links, referential integrity checks, and creating applications in Access.

    I don't believe Microsoft Office is great software. But I do recognize that there are users who are using it far more sophisticated ways, who are not served by the current open source offerings.

    The same with Photoshop in this article. The majority of users using GIMP are cleaning up vacation photos from their digital cameras or putting celebrity heads on animals. To the majority of people using GIMP would be equally well-served with any of the dozens of paint applications out there.

    But professionals need more, much more. And most importantly, they aren't just using Photoshop itself, but also many of the third-party add-ons that make Photoshop a platform.

    If the open source community wants to say, "hey, we've got some great applications that do the job for most people," then I fully agree. It's the people who don't seem to know that there is a level of sophistication beyond what they know who I have a problem with.

    1. Re:It's Not Enough by Max_W · · Score: 1
      --They don't do simple data analysis with Access, they are constructing huge databases with sophisticated relational links, referential integrity checks, and creating applications in Access.--

      "Huge databases with Access". Oh gosh! This sounds like an evil joke to me. Access is the intentionally crippled database. If you wish a bit less crippled database, pay more for a bit crippled MsSQL some limited edition, an so on until you reach MsSQL enterprise edition, which would cost a fortune.

      As for GIMP, it is the masterpiece of software. I have got Photoshop, but it is the Adobe. Have you ever tried to open an Adobe PDF file in browser? The GIMP compares to Photshop about the same as HTML webpage with the PDF page opened in browser.

      The art made in GIMP has its flavor, its poetry. GIMP rocks. If you say that Photoshop is better than GIMP, than you did not use GIMP seriously.

  179. Port Photoshop in one day by ChrisMaple · · Score: 1

    Package photoshop with wine. Wine needs to be properly configured to run photoshop. Include all the required dlls.

    --
    Contribute to civilization: ari.aynrand.org/donate
  180. Why Photoshop by ratboy666 · · Score: 1

    If you need Photoshop, or are happy using Photoshop, then use it. On Mac, or Windows, or whatever platform it runs on.

    If, as the article mentions, Photoshop is a Platform, and not just a piece of software, you really don't have a choice.

    Maybe it will be released for Linux, maybe not. It almost certainly won't be released for SGI IRIX, or SUN Solaris.

    That's pretty much all there is to that discussion.

    ===

    Except that it leads to another question -- Why is Photoshop a platform OUTSIDE the limited area of Graphics Arts? In other words, why do a lot of people, who otherwise shouldn't care, use it?

    For example, MS Excel is comparable with (say) GNU Gnumeric. I can't swear to the LATEST Excel version, but previous versions did really bad stats calculations. So, I used Gnumeric. However, MOST PEOPLE DON'T CARE ABOUT STATS! Exel is "good enough". People who did care, switched. In a similar vein, GIMP should be "good enough" but it isn't. Since Photoshop is quite expensive, more people should be happy with the "good enough" GIMP.

    I don't do CMYK separations. I print pictures, and then forward stuff electronically to a publisher. The publisher can take care of it from there. She knows what to do (including "Photoshop").

    There IS a reason that Photoshop is popular. "Photoshop" has become a common verb. There is an underground of "Photoshop" knowledge. Graft a head onto this picture &etc. And it must be easy to bootleg Photoshop. Otherwise it sure is an expensive way to "goatse" your photographs.

    An interesting way to make money -- encourage bootlegging to provide a base, and then charge a fortune from the professionals.

    Ratboy

    --
    Just another "Cubible(sic) Joe" 2 17 3061
  181. I ask myself seriously.... by drolli · · Score: 1

    if more than 10% of the posters here have ever used Adobes Graphics Suite for some time > 3 Month in daily use AND gimp also for the same amount of time on at least similar tasks. I do not believe so; after a few days Adobes products (i.e. Illustrator) kick the ass of all other Drawing/Image modification (unspecialized) Tools, if run on decent Hardware AND used for creating printable Documents. The UI is a little bit strange for a few days and featuritis does not make things better in the beginning, but when you get the concepts, which are less counterintuitive than the xfig GUI, the UI is very efficient. On the other hand: for most photo operations I use the gimp. Before Adobes procuct has finished loading the plugins on my computer, I am already done with editing using xfig or gimp and there are functions in the gimp which I actually did not find in Adobes products, since everyone who wants to play around is encouraged to do so. And I scripted the gimp when scriping was an unknown word in drawing/painting programs.

  182. Re:I just refuted this article's mistakes yesterda by dozer · · Score: 1

    Wow, you are really out of touch.

    Did you even click on the link you gave for CMYK support? Separate is just a rudimentary plug-in. Proper seps are deeply complex and require core support to be done properly. Even the Gimp developers agree that CMYK is simply not supported. Why would you pretend otherwise?

    And then you bring up Cinepaint as an example of the Gimp supporting 16-bit pixels?? It has been almost SIX YEARS since CinePaint could be considered a part of the Gimp. From your own link, "CinePaint is undergoing a transition from being a monolithic GTK-based tool to a constellation of applications that use FLTK." Dropping CinePaint is, in my opinion, the worst decision that the Gimp project ever made. In the past six years CinePaint has thrived while the Gimp has pretty much stagnated. Oops.

    So, you must agree that the *Gimp* supports neither CMYK nor 16-bit, right? If not, have you got that LART handy? You may need a healthy dose of it...

  183. Hmmm. Quite a problem. by jd · · Score: 1
    I just want to clarify one thing, though. When you say that the GIMP "has no interest" in supporting 16 bits per channel, would I be correct in taking that to mean that the GIMP developers have been approached on this but have stated that it's not something they're interested in supporting?


    If the answer is "yes", I'm moving the item up my to-do list. That's exactly the sort of situation that does get to me. Coders have every right to decide what they want to code and what patches they want to accept, but there is a big difference between being selective and becoming stagnant. Selective is necessary. Stagnant is best left to swamps and marshland.


    In fact, if early coders had kept pace, the GIMP might never have been written. Between existing painting programs, the Utah Raster Toolkit and xv, early image manipulators had plenty of resources. At least, for the time. Those tools have long-since rusted.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Hmmm. Quite a problem. by gorim · · Score: 1

      Well, I based my statements on the following:
      1. GIMP does not support working directly in >8-bits / channel.
      2. All of my searches of the internet have found occasional discussion from GIMP developers who stated that there is no need for >8/channel due to 8/channel being more than adequate for the eye.
      3. GIMP documentation almost completely ignores the issue of channel bit depth.
      4. There is a surge of commercial applications for professional digital image manipulation for handling RAW files. Take a close look at Apple's Aperture. Sure it can work in any format, but its whole concept was built around RAW 16bit/channel.
      5. A search of the internet on professional digital photo RAW work flows shows much discussion about why those extra bits should never be thrown away.
      a. They represent much additional detail (a bit less than 4096 levels of detail, as opposed to the normal 256) that can be "pulled-in" and manipulated to form a final downconverted 8-bit/channel image.
      b. Artifacts from many applied filters/transforms are greatly reduced before the final 8-bit/channel downconversion.
      6. My own experience confirms this.

      Final conclusion: GIMP developers have their priorities, I do not begrudge them that. I conclude there are not many such developers who use GIMP themselves purely for RAW digital photo workflows. However, the very recent huge surge of cameras outputing these formats are driving a corresponding increase in the number of people demanding such features. Again, the professional marketplace is abound with such examples.

      But in the end, it means a segment of the population that will never want to use GIMP.

      And believe me, I very much wanted to use GIMP, I did not want to go to Photoshop, but I ended up paying money (yes I buy rather than warez my non-free/OSS software) for the bottom-end Photoshop Elements 3.0 for my Mac because of those features. There are many other packages out there too I can spend money on, but very few free ones.

      The dcraw packages are fantastic, I have occasionally used them for batch conversions. I haven't tried the GIMP plugins because the down-conversion to 8-bit happens too early in the workflow. The free software that came with my camera (from Canon) is not bad and works in a pinch.

      I would use GIMP in a heart-beat if but for that one feature. Without it, I can't really use it at all, because the commercial apps offer comparable feature-sets, I may as well avoid time consuming import/exports and stay in them.

      I am lucky, I do not do digital photography for a living. Those that do, can't always afford the big expensive packages and softwares. A free OSS solution would help out alot of journalists and photographers who could use more free solutions on their tight budgets.

  184. Yes, they have a point, but it's the wrong one :) by CarpetShark · · Score: 1

    I'd be the first to admit that GIMP is annoying. I've asked them many times to re-do the GUI. Look at projects like K-3D for evidence that massive GUI changes can be made, in complex software, if you care about users. BUT, I also want to point out that Photoshop is absolutely NOT the be-all-and-end-all of bitmap image editing. I'd much prefer to see a vector/bitmap combo package, like Xara are now developing as open source, or something like Corel Draw/Paint. Photoshop is basically an over-developed retouching utility, not an art program.

  185. GIMP just works by Max_W · · Score: 1
    GIMP just works, like Apache, PHP, MySQL, Firefox, Thunderbird, it is the honest nice piece of soft.

    Updates are often and free. With every version it keeps improving. It is made by artists for artists.

  186. I'm seeing a lot of complaints... by Anonymous Coward · · Score: 0

    ...but no one offering to write a different GUI for GIMP. Stop bitching and do something about it.

    Is it not possible to fork the code? Maybe call it the PIMP fork (Pleasurable Image Manipulation Program)?

    If forking is not allowed, then just write a plug-in that has an improved GUI. Or something. My point is, this is something YOU can do something about. Stop whining and do it.

  187. Biggest GIMP complaint by Felonious+Ham · · Score: 1

    The GIMP is a fabulous tool, but: I hate the floating tool windows--having to click around to find the tool window I need. This is not a complaint specific to the GIMP, Inkscape and XSANE have a similarly frustrating interface. I could live the floaty bits if they would just make all windows raise to top if you clicked on any part of the application.

  188. nuts by twitter · · Score: 1
    The issue is the accumulated filter effects and transformations 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 noticeably visible in the final image.

    Well, duh, that's what internal representations are for and it has nothing to do with what I was saying. When I write an image filter, I use a 32 bit float for each channel, regardless of the input file type. Gimp does a similar trick. General input libraries handle file formats. My point was that it's unlikely that a camera will be able to capture 16 bits per channel, your eyes can't tell the difference and that people who spend big bucks on such devices are usually wasting their money. That's double the case if the camera maker uses some silly format for storage representation that they won't tell anyone about.

    --

    Friends don't help friends install M$ junk.

    1. Re:nuts by gorim · · Score: 1

      Still missing.

      Doesn't matter that you use a 32-bit float per channel for your filters. If you operate on 8-bit channels, thats alot less *data* for you to operate on than if you had 16-bits of data.

      Now granted, current digital cameras really only capture 12-bits at raw. But consider what that extra 4-bits can do, thats a range of about 4096 above the range of 256 that exists in 8-bits. You can do ALOT of things with this extra data like varying exposures that you simply cannot do if the data isn't there to begin with. Your 32-bit float representation for your filter doesn't do a bit good operating on data that was thrown away.

      Now, to drive my point home, real photographers do real things with this data every day, and it translates to real visual effects that is extremely useful in the final output image, even when that image ends up being downconverted to 8 bits per channel.

      This is why nearly every photo manipulation program out there, except for gimp of course - gimp's missing the boat, allows for operating at this bit depth. These features exist because they translate into real valuable operations.

  189. Re:I just refuted this article's mistakes yesterda by Hosiah · · Score: 1
    Sweetheart, sit down... CMYK has lots and lots of patents involved. The *best* support you could get in Gimp is a work-around. If you want better than that, the people to complain to don't work for Gimp.

    As for Cinepaint, I'm going out on an extremely short limb and guess that you've never run it. I have. I've run more programs than you could count. Cinepaint, included in say, for instance, MediainLinux IS Gimp, with fewer plugins and 8/16/32-bit support and a sexier name (since everybody harps on the name). Same interface, same menus, same multiple windows everybody harps on. I addressed all that you bring up in this post, and considered it too bleeding obvious to repeat.

    You can get one point back if you can even tell me the origins of the term "LART".

  190. Save for the web by Anonymous Coward · · Score: 0

    Hate to bust your chops, GIMP apologist, but Photoshop's Save For The Web has MORE choices than GIMP. More controls. More features. More details.

    You clearly never use Photoshop or you would have understood the GP's point about the measily, paltry GIMP output offerings versus the comparatively deep and robust offerings of Photoshop.

    You are indicative of the GIMP fanboys who have NO IDEA what Photoshop users need. And have.

    "That is why you fail."
                        -littlegreendude

    1. Re:Save for the web by SillyNickName4me · · Score: 1

      Heh, that calls me fanboy...

      I currently have the save for web dialog in front of me, and I fail to see an option there that isn't in the Gimp, tho at differnet places often. Yeah, you'll have to do it in a slightly different way, very inconvenient if you ae used to doing things the Photoshop way already.

      I still do not see the point of this dialog however, there is nothing inherently different about graphics used on the web when compared to other uses. Yeah, all uses have their specific requirements for quality (resolution, color space and depth etc), so why not have a 'save for press' option as well? and how about a 'save for later printing on a inkjet printer' and don't forget a variation for a laser printer, save for screen (with options for different screensizes of course)

      The one good thing I can say about the 'save for web' dialog is that it gives somewhat of a preview so you can make a guess at how it will look with the settings you are using. That said, seeing how browsers tend to scale pictures to whatever size fits them nowadays, and use pretty bad algorithms for that (nearest neighbor), the final result is often not going to be what you have on your screen there anyway (and you don't need a seperate 'save for web' dialog for that really)

      When you 'need' that dialog, you seem to have learned what to click on to achieve a specific effect, without understanding what you are actually doing, and that is exactly the thing I have run into with quite a few photoshop users. They learned from tutorials, but have no real idea about what they are doing.

      Oh, and please, a dialog collecting a bunch of options is not a 'module', or are people suggesting that untill this 'module' got introduced, Photohop was lacking in the area of color reduction and/or scaling, or didn't support jpeg or gif or such?

  191. A partial solution for GIMP/RAW interaction by Explo · · Score: 1

    UFRaw and dcraw appear to give me a nice way to load RAW photos into the GIMP. The conversion from RAW is done with 16-bits per component accuracy, although the end result will then be sampled down to 8 bits per component. Obviously, this is not quite the same as having the 16-bits per component accuracy available all the time, but at least things like color balance, brightness/gamma etc. can be tweaked within the more accurate representation before the downsampling.

    --
    Everyone who makes generalizations should be shot.
  192. PS used by pro's by sad_ · · Score: 1

    And there are so many gfx-pro's using linux that it turns out at nr.1 of the most wanted apps list? What does it mean, Linux desktop is used most by gfx artists?

    You're kidding right, a bunch of people just filled in some app because they want PS (and only PS) and not Gimp (or any other linux alternative). I wonder why, 90% of the people don't even need all the power that the gimp gives them.

    --
    On a long enough timeline, the survival rate for everyone drops to zero.
  193. average joes won't like gimp by amigabill · · Score: 1

    I only know onw person using Photoshop on a Mac, but he's in the graphics design biz. I know a lot of everyday PC users who use "photoshop" as a verb when they need to edit a photo, remove the two-finger bunny ears, redeye, etc. These aren't Macheads or Linux geeks, these are average PC users.

    I've used gimp a little. More accurately, I've tried to use gimp a little. I wasn't very successful, and I wanted to do some extremely basic stuff like make a jpeg with some text in it. I couldn't figure out how to crop off extra margins around the text I managed to create. In trying to place a couple lines of text, it kept doing weird things and one of the lines was sortof faded, as if it was stuck in some mode I didn't understand or know how to get out of. Granted, I didn't read any howtos or anything, but it was such a stupidly simple thing that would have been extremely easy in MS Paint, but I only have a Solaris box at work and I learned to hate the gimp.

    I've never used Photoshop myself at all. If it's as hard to figure out such a simple thing as it was in gimp, then I don't want to. For the love of god I hope it's more intuitive than gimp is. For myself, given the choice between gimp and some other tool I've never used before, I'll take the one I'v enever used before, as I already know I'm not productive with gimp.

    Might gimpshop be the answer? Possibly. It's not as easy as "emerge gimpshop" though, so for my home linux box I'm probably too lazy and will just boot into Windows and use paint, or use an old Amiga program I like, and at work I'm pretty much screwed but luckily I don't have to deal with such things at work very often.

    It doesn't matter how powerful or what feature set gimp has. Often average-joe business types get the final say, and if they can't get gimp, then they won't sign off on it. If they're accustomed to Photoshop, that's what they'll prefer to stick with. If I was a businessman, I'd prefer to avoid gimp based on my personal experience with it so far. Photoshop is a big brand name that will of course be in demand.

    I think a better idea than trying to convert Photoshop users to gimp is to get Photoshop well supported in Wine. Maybe it already is. Get a good IT guy to deal with supporting it as surely Adobe won't, and the users can have their favorite tool, and businessmen can choose Linux while keeping with the big graphics brand.

  194. No offense... by loqi · · Score: 1

    I love KDE and all, love it, but that's still basically an insult to Photoshop and Photoshop users.

    --
    If other reasons we do lack, we swear no one will die when we attack
  195. Documents and Folders by Dan-DAFC · · Score: 1

    People have used the terms Folder and Document since long before Windows 2000. Something isn't new just because you hadn't heard of it.

    I believe Microsoft introduced the terminology with Windows 95. DOS, like Unix, had "files" and "directories". Folders and documents probably make more sense to an inexperienced user since they correspond more closely to real world equivalents. In the real world documents go in files (folders). The term folders was no doubt chosen to avoid confusion with the legacy use of the term files.

    --
    Suck figs.
  196. GIMP will be surpassed, not fixed by Julian+Morrison · · Score: 1

    People have been complaining about the GIMP UI for ages. The coders have made efforts to reduce the pain. However, as far as I've ever seen, very few open source programs ever get their UI iteratively improved towards perfection. As with Eclipse versus Emacs, they're surpassed by newer programs with fresh UIs, more modern design ideas, better dev methods.

  197. Who's taking offense now? by BlueLightning · · Score: 1

    that's still basically an insult to Photoshop and Photoshop users.

    Eh? Where's the insult? He merely suggested a Linux alternative that might be more suited to Photoshop users than the GIMP.

  198. yep... by Cryptnotic · · Score: 2, Insightful

    If the GIMP people needed to make money off of the software, they would be required to listen to what the users wanted. However, they don't. So they can make a piece of software that pleases themselves, programmers who sometimes dabble in image manipulation.

    --
    My other first post is car post.
  199. Real world example and explanation by gorim · · Score: 1

    I uploaded two images to this gallery at http://www.pbase.com/gorim/raw_workflow

    Basically it shows one of the reasons why one would need to work at 12-16 bits / color channel, with full sized sample images I took and processed.

    I am working on a second example, one that shows introduction of artifacts when too many filters/transforms are applied to an 8 bit / color channel image (as one might need to do in reality, as opposed to arbitrary manipulations that could make anything look bad).

    This thread has mostly died down, but hopefully people who are interested still manage to take a look and if it helps spur GIMP development, so much the better.

  200. Re: Adobe Acrobat on Linux... by peterpi · · Score: 1

    Because Acrobat 7.0 is not Acrobat version 6?

  201. GIMP UI is OK to me by Max_W · · Score: 1
    I use GIMP for ages for complicated work. I processed thousands of images with it.

    I tried photoshop, but I do not like it. Maybe because I do not like Adobe in general, especially its PDF format and especially when it is placed on the web. PDF freezes my browser (and computer) and I have to loose my time on this stupidity.

  202. Re:I just refuted this article's mistakes yesterda by dozer · · Score: 1

    The *best* support you could get in Gimp is a work-around.

    That may be true but it's not due to patents. Basic CMYK is supported in the new Krita, and work is progressing on color cal and Pantone seps. If patents are not a problem for other projects, why are they showstoppers for the Gimp? If you want to discuss this further, how about posting the #'s of the potentially infringing patents?

    Cinepaint, included in say, for instance, MediainLinux IS Gimp

    Yes, old Cinepaint was derived from the Gimp. But, as you say, it doesn't have many features and all further developemnt is dead. Unless someone steps up to maintain and merge it, it's irrelevant for the discussion at hand (I'm not holding my breath). If you recall, we're talking about whether or not the *Gimp* can do better than 8-bit channels. And it can't.

    So, my points are secure. But, hey, a point to you for knowing how to look something up in the Jargon dictionary!

  203. Stagnation by Trogre · · Score: 1

    It seems the GIMP project has stagnated, exemplified by some bad decisions in the past (see non-cooperation with FilmGIMP/CinePaint).

    Is it time for a fork, a la XFree86/X.org?

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  204. GIMP does suck by Anonymous Coward · · Score: 0

    "Who says it sucks? You? Maybe the some people think it's great."

    I gave it an honest try, but eventually removed it. I cringed every time I used the perverse "go out of its way to be difficult" file load/save interface. A good example of the poor planning that went into it is found in the Rotate command. There is a crippled, useless verison of Rotate command, easily found in a menu where it is supposed to be. The usable full-fuction Rotate (with the same name) is buried deep inside a tools/extras/etc menu. They never thought to only have one Rotate (a good one) and make it easy to find.

    It comes across as a shareware written by a middle-school kid (the kind where the kid writes it and nobody ever likes it enough to register and pay him). Or, perhaps like a "camel" because we know more than one person wrote it. Ever hear the joke that a camel is a horse designed by a committee?

    I bagged it and went back to Paintshop 4.14. You know, the one that is about 10 years old, and looks much more up-to-date and refined than the latest kludge of a GIMP.

  205. Unfortunatley, finding the place to click... by leonbrooks · · Score: 1

    ...can be a bit of a bastard, and when you do find it, the newly installed software might not work, or might break something else.

    For a case in point, the wireless on this laptop is unreliable under MS-Windows XP and bulletproof under Mandriva Linux 2006.0; it was even less reliable until I figured out that ZoneAlarm kept forgetting to allow DNS access to fully-blessed programs (I had to give it carte blanche on DNS), and finding that out was pretty obscure.

    Installing stuff on Mandriva Linux is a breeze, you just scroll down to it in RPMdrake, click on it and here comes the package and everything it needs to survive. I understand that Synaptics, YAST and friends are pretty much the same. On MS-Windows, you first have to search out the program (forex, on TuCows) and a program to do what you want may not be available from a trusted supplier, so you probably have to install it "blind" from some random site on the net -- or three or four of them. And even the ones without nastyware enclosed might have specific, conflicting prerequisites, in which case you're screwed: pick your favourite and delete the other(s). If you can. Under Linux I have the option of pulling down an SRPM (the source! shock, horror) and clicking on it to have the machine make a version tailored to itself. Oh, yes, and if you delete a package (using one central tool), it's really gone (it and optionally any dependencies unique to it).

    VB is an effing nightmare to maintain, or to build anything really large in. Use Ruby and FreeRIDE instead -- yes, even on MS-Windows.

    --
    Got time? Spend some of it coding or testing