Live data from Hacker News

Switch from Photoshop to Gimp: Tips From a Pro

rileybrandt.com

81–90 of 130 posts

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

#81
post #47
post #37

Earlier quoted context omitted.

Shouldn't you know what you want to to, if you're a professional? If you don't know what you want to accomplish, you need to experiment. This is when those non-destructive features come in handy, but if you know the goal and how to achieve it, they aren't necessary.

"Shit's Easy Syndrome": http://steve-yegge.blogspot.com/2009/04/have-you-ever-legali...

I'm not saying this stuff is easy.

I'm saying professionals (people who are skilled in non-easy stuff) know what they want and just do it.

Probably there are just many people out there who using PS and aren't professionals, which is okay...

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

#82
post #51

Earlier quoted context omitted.

I like Paint.Net a lot on the windows side... for Mac/Linux alternative, look into Pinta http://pinta-project.com/ ... it's essentially a cross-platform port of Paint.Net They do the vast majority of what most people need in a simple photo editor.

Looks like a clone rather than a port (as paint.net isn't open source you can't really port it), but I'll take a look. Their github ( https://github.com/PintaProject/Pinta ) makes it look like the project may be abandoned.

It's a port of Paint.net 3.3.6 from .NET to Mono. Paint.net used to be MIT-licensed, and 3.3.6 was the last version that was released open-source.

Besides, the UI in Paint.net 4.0 has been rewritten to use WPF. That makes it essentially impossible to port to Mono.

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

#83

I haven't tried it myself so can't vouch for it but GimpShop ( http://www.gimpshop.com/ ) fills a similar niche.

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?

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

#85
post #3

This reminds me of the endless bug reports we're getting right now about the Octave GUI not being indistinguishable from Matlab. Makes me wish people weren't so inflexible about the tiniest UI differences. It's difficult to please the converts.

It's not that people are inflexible, it's that if you're going to provide an alternative, it should slip itself into someone's workflow and processes with almost no inertia. When someone is accustomed to hitting a keystroke to achieve a certain effect, or someone is using to having a widget in the left corner, any change to that process is going to cause discomfort, and most people don't need that.

A lot of people just never seem to become accustomed to anything in particular, so these changes don't bother them. Nothing wrong with that (it takes all sorts), except that I've a strong suspicion that it is these people who then keep changing the keyboard shortcuts, moving the icons around, poking at everything so it looks totally different, and then removing the macro functionality. Because I guess they just have no idea how traumatic this sort of thing is.

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

#86
post #42

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…

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

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

#87
post #81
post #47

Earlier quoted context omitted.

"Shit's Easy Syndrome": http://steve-yegge.blogspot.com/2009/04/have-you-ever-legali...

I'm not saying this stuff is easy. I'm saying professionals (people who are skilled in non-easy stuff) know what they want and just do it. Probably there are just many people out there who using PS and aren't professionals, which is okay...

I note that it has taken you - so far - two attempts to make your point ;)

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

#88
post #81
post #47

Earlier quoted context omitted.

"Shit's Easy Syndrome": http://steve-yegge.blogspot.com/2009/04/have-you-ever-legali...

I'm not saying this stuff is easy. I'm saying professionals (people who are skilled in non-easy stuff) know what they want and just do it. Probably there are just many people out there who using PS and aren't professionals, which is okay...

[deleted]

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

#89
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 find it disheartening. Why work on something that will forever suck and not be a competitor, and can't implement the full list of features because we don't have the giant budget of our non-free competitor?

But then I remember that people are typically more flexible than they appear to be when they write these lists, and you'll discover that they may do without some of the features that they list, at least in some circumstances. And that there exist many other people with different lists of sine qua nons who will use the free as in freedom alternative you're working on because they have different needs.

So, to the OpenNote developers and to anyone else implementing a FAIF replacement I say this: don't let these giant lists of features and suggestions about how you'll never be competitive grind you down. There are many people out there who will appreciate your work, sometimes even the people who compiled these lists. Look at the lists, see what you can implement, and don't be disheartened by the parts that seem impossible to implement. Who knows, maybe some day someone will come along and help you implement the parts that seem so hopeless to you.

Keep your chin up, free software devs!

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

#90

Earlier quoted context omitted.

I don't think you can just buy photoshop anymore. You have to subscribe to it for a monthly fee

You can still get CS6, but CC, which was equivalent to CS6 when it started, is coming up on a year old, and you pay 20 dollars a month to have access to it. CC will continue to get updates. When you stop paying your 20 dollars, you stop having Photoshop at the end of the month.

There was actually a $10/month offer for Photoshop CC and Lightroom CC (expires 31st March) - I got bought it for my other half. At $120/year it's cheaper than buying Lightroom in full here in Australia.

The frustrating part is that you can't pay for the full year up-front for most Creative Cloud plans.

Post reply on HN