News for hackers. Stuff that matters.
Re:Too Many Knobs by TeMPOraL on Friday June 10, 2016 @04:59AM (#11875123)
sigh

That's how you get shiny toys, not useful tools.

The advice here is good if your primary goal is to successfully sell glorified interactive ads in a market where people buy software by looking how pretty it is and making their choice in 2 seconds. If that's your goal, then ok, one has to make a living, but in this case I don't want your software, and I'll discourage everyone from using it.

Sane defaults + flexibility are a way to go. Software should empower the user, and part of this empowerment may be suggesting a particular workflow, but it should not force one to use that workflow and never stray from it. And don't give me the excuse that "more options == much more complexity == much harder to add new features". That's only true if you write utter spaghetti code, and fuck it, programmers get paid so much so that they do this right.

Re:Too Many Knobs by eterm on Friday June 10, 2016 @08:45AM (#11875949)
Emphasis on sane defaults.

One issue is that "sane" changes over time, but it's hard to change defaults without upsetting people who suddenly find their defaults changed because of an update.

(Although I'd argue that's best solved by letting them be upset until they understand why the default changed.)

e.g. a Video capture which previously defaulted to 320x240 might later default to 640x480 and now default to 1440x720.

Re:Too Many Knobs by thaeli on Friday June 10, 2016 @10:12AM (#11876455)
Or better yet, intelligently handle the change as a suggestion during the upgrade process. "We see you are still using the legacy default 320x240 setting. We are now recommending 640x480. Do you want to change to this new recommendation, or keep your existing setting?" Something like that.