3 ms·

Not sure why you're getting downvoted. I completely agree. I use photoshop maybe once every two months and have found that its interface is completely inaccess

by bpchaps 10y ago

Not sure why you're getting downvoted. I completely agree. I use photoshop maybe once every two months and have found that its interface is completely inaccessible if you don't use it full time. I understand that it's great to have full control over everything, but there's a point where it's overkill in Getting Shit Done. Hell, it's gotten to the point with me where I'd rather use cv2 over photoshop/gimp for most things...

Programmatic 10y ago
Meanwhile, I fire up the average application that uses the Gnome HIG spec, and I find it horrendous to use. They take it a number of steps further and remove, completely and thoroughly, any ability to customize. I very much like the Apple mentality circa 2005 with sane, intelligent defaults, a small number of configuration options in a small number of screens, and an advanced button for everything else. Apple did a very good job back then of making their software feature complete and customizeable without making it a shit show in either the too dumb or too complex direction.
- bpchaps 10y ago
  There's a middle ground. I'm fine with tons of configuration, but at least make some sane defaults or prompts so that I don't have to read a giant wiki to do an initial setup. Everybody initially runs through it, so why not spend the time it took to write the wiki and write prompts for an installer, instead?
Bartweiss 10y ago
Bear in mind, though... This study profiled MySql, Hadoop, Apache, and Storage-A. None of those are casual-user tools, and removing feature options, even rarely-used options, would be a serious and unjustified breaking change.
- bpchaps 10y ago
  Right, I get that, and I still agree. There are WAY too many features in these things that should definitely exist, but sane defaults would go a long way. Really, I'm tired of being told "read the documentation" and "You just haven't used it enough" when documentation is given 5% of the energy it should be given. I'm convinced that the only reason so many SV projects exist because of bad config management in OSS projects.
nucleardog 10y ago
Chances are Photoshop is the wrong tool for you. It's the wrong tool for a lot of people. It doesn't make Photoshop a bad tool or overkill. It makes your choice in using it bad, and makes it overkill for your specific task. A nail gun isn't a bad tool because a hammer is simpler and more intuitive, and a hammer isn't a bad tool because a rock is simpler and more intuitive. We don't expect roofers to use rocks, and we don't expect someone hanging a picture up to use a nail gun. Specialization is not a bad thing.

by bpchaps 10y ago

Programmatic 10y ago

Meanwhile, I fire up the average application that uses the Gnome HIG spec, and I find it horrendous to use. They take it a number of steps further and remove, completely and thoroughly, any ability to customize. I very much like the Apple mentality circa 2005 with sane, intelligent defaults, a small number of configuration options in a small number of screens, and an advanced button for everything else. Apple did a very good job back then of making their software feature complete and customizeable without making it a shit show in either the too dumb or too complex direction.

bpchaps 10y ago
There's a middle ground. I'm fine with tons of configuration, but at least make some sane defaults or prompts so that I don't have to read a giant wiki to do an initial setup. Everybody initially runs through it, so why not spend the time it took to write the wiki and write prompts for an installer, instead?

Bartweiss 10y ago

Bear in mind, though... This study profiled MySql, Hadoop, Apache, and Storage-A. None of those are casual-user tools, and removing feature options, even rarely-used options, would be a serious and unjustified breaking change.

bpchaps 10y ago
Right, I get that, and I still agree. There are WAY too many features in these things that should definitely exist, but sane defaults would go a long way. Really, I'm tired of being told "read the documentation" and "You just haven't used it enough" when documentation is given 5% of the energy it should be given. I'm convinced that the only reason so many SV projects exist because of bad config management in OSS projects.

nucleardog 10y ago

Chances are Photoshop is the wrong tool for you. It's the wrong tool for a lot of people. It doesn't make Photoshop a bad tool or overkill. It makes your choice in using it bad, and makes it overkill for your specific task. A nail gun isn't a bad tool because a hammer is simpler and more intuitive, and a hammer isn't a bad tool because a rock is simpler and more intuitive. We don't expect roofers to use rocks, and we don't expect someone hanging a picture up to use a nail gun. Specialization is not a bad thing.