Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Switch from Photoshop to Gimp: Tips From a Pro

rileybrandt.com

Post reply on HN
Print view View original

91–100 of 130 posts

Re: Switch from Photoshop to Gimp: Tips From a Pro

#91

Post by Glyptodon »

dperfect wrote: post #14

If you're using Photoshop for the purpose it was designed for (editing photos, not illustration/painting from scratch), then GIMP is absolutely inferior in its current form. If you're making edits directly to source pixel layers (or even making duplicate flattened layers and working on those), you're doing it wrong. Photoshop is designed for non-destructive editing. An essential part of that is adjustment layers. Man…

Photoshop might be called photoshop, but I don't get why anybody would edit photos with Photoshop, Gimp, or any other similar editor rather than a decent RAW editor, be it Lightroom, Darktable, Aperture, or AfterShot.

Re: Switch from Photoshop to Gimp: Tips From a Pro

#92

Post by elsamuko »

jordigh wrote: post #89
jjcm wrote: post #62

This was posted to reddit a couple weeks back, and I'll repeat the same comment I made there. "I spend about 90% of my time in Lightroom and only 10% in Photoshop." This is why he was able to do this. He isn't using the functionality that Photoshop provides, he's using the functionality that Photoshop Essentials provides. Look at his parity instructions - every feature is found in Photoshop Essentials. If that's all…

I hear this stuff all the time. So this is my own canned response: https://news.ycombinator.com/item?id=6675258 > it has a ways to go before it will actually be a competitor. And it doesn't have a few features that I find incredibly invaluable as an Evernote user: [list of features snipped out] As an Octave developer, I frequently hear exactly the same things about Octave vs Matlab, and if I listen too closely, I fin…

Octave is awesome! Keep up the good work. At university everyone was begging for Matlab instances from the licence server, while I had 6 instances of Octave open :)

Re: Switch from Photoshop to Gimp: Tips From a Pro

#93

Post by gaius »

tavoe wrote: post #75
dperfect wrote: post #32

Earlier quoted context omitted.

The thing you're missing is that the differences between GIMP and Photoshop are not just user interface idioms. I wish it were that simple (I'd love to switch to GIMP if I could). It's not a matter of "learning something new"; it's the fact that without real non-destructive editing features, GIMP is basically just an enhanced version of MS Paint in the hands of serious photographers and retouchers. Non-destructive ed…

I'm totally ignorant in this field. If you're worried about messing up a file, why not just make a copy of it before you edit it?

Never used version control on your code?

Re: Switch from Photoshop to Gimp: Tips From a Pro

#94

Post by plasticbugs »

CatMtKing wrote: post #83
plasticbugs wrote: post #36

Earlier quoted context omitted.

I originally created Gimpshop, but I'm not the jerk who owns that domain and added adware & spyware to the source. Sorry about that. I hate that this guy is out there making my fun little project into an abomination.

Man, that sucks. Do you have a project site for your real source code?

I don't have a project site for it. I became discouraged after this whole ordeal and I let it slip away into obscurity. Also, when I put Gimpshop out there, I didn't really know how to code, so updating the source to stay current was a huge undertaking for me. Since then, I've become a self taught programmer. I know Ruby fairly well. I've built a couple of non-trivial Rails sites and within the last 6 months, I published my first iOS app. Gimpshop was a fun little 'prank' that got bigger than I ever expected. Sad what it has become, though.

Re: Switch from Photoshop to Gimp: Tips From a Pro

#95

Post by jebblue »

EpicEng wrote: post #86
jebblue wrote: post #42

Earlier quoted context omitted.

>> and one that apparently the GIMP devs seem to be ignoring If you can code then contribute the feature, if not then hire someone to write it and contribute it and if neither then at least file a bug/feature request.

Or, in the real world, where people just need to get shit done and do not know how to program, I'll just buy photoshop. Why in the world would I spend more , in time or dollars, to add a feature to Gimp which already exists in Photoshop?

Did you read my suggestion as dictation? It was just a suggestion, nothing more, if you prefer PS, go for it, no worries.

Re: Switch from Photoshop to Gimp: Tips From a Pro

#96

Post by buddhirons »

adamwong246 wrote: post #58
dperfect wrote: post #32

Earlier quoted context omitted.

The thing you're missing is that the differences between GIMP and Photoshop are not just user interface idioms. I wish it were that simple (I'd love to switch to GIMP if I could). It's not a matter of "learning something new"; it's the fact that without real non-destructive editing features, GIMP is basically just an enhanced version of MS Paint in the hands of serious photographers and retouchers. Non-destructive ed…

Perhaps off subject but I think there is a need for a non-destructive, functional script-based image editor. I find, as a programmer, I prefer using ImageMagick when I can. Wouldn't it be nice to have the intuition of a UI backed by scripting? Imagine that at each step in your function, you can tweak it using traditional ui tools and the "tweaks" are automatically reflected in the script. To get the final export, you…

One can script both photoshop and gimp. I spent a year and a half writing scripts against Photoshop and gimp has a batch mode in a CLI.

One used to be able to record a macro in Photoshop and export it to a script that one could call from a visual studio project. The code it produced was barely human readable but it was helpful for discovery.

Re: Switch from Photoshop to Gimp: Tips From a Pro

#98

Post by EpicEng »

jebblue wrote: post #95
EpicEng wrote: post #86

Earlier quoted context omitted.

Or, in the real world, where people just need to get shit done and do not know how to program, I'll just buy photoshop. Why in the world would I spend more , in time or dollars, to add a feature to Gimp which already exists in Photoshop?

Did you read my suggestion as dictation? It was just a suggestion, nothing more, if you prefer PS, go for it, no worries.

I am saying that yours is a poor and unrealistic suggestion.

Re: Switch from Photoshop to Gimp: Tips From a Pro

#99

Post by copergi »

jjcm wrote: post #62

This was posted to reddit a couple weeks back, and I'll repeat the same comment I made there. "I spend about 90% of my time in Lightroom and only 10% in Photoshop." This is why he was able to do this. He isn't using the functionality that Photoshop provides, he's using the functionality that Photoshop Essentials provides. Look at his parity instructions - every feature is found in Photoshop Essentials. If that's all…

>He isn't using the functionality that Photoshop provides

And since that is the same for the vast majority of photoshop users, he provided a super helpful guide for them. It does not say "how everyone can switch to gimp".

Re: Switch from Photoshop to Gimp: Tips From a Pro

#100

Post by _delirium »

windsurfer wrote: post #76
neovive wrote: post #64

Earlier quoted context omitted.

I use InkScape on the Mac. To get the most recent builds running, you need install XQuartz which is not bundled with recent OS X versions.

Even the latest XQuartz install appears to be 3 years old. Were you able to find a more recent one? I would be very interested if such a build existed.

I don't know of a standalone installer, but Macports has the current stable version (0.48.4).
Post reply on HN