News for hackers. Stuff that matters.
Re:Too Many Knobs by jdmichal on Friday June 10, 2016 @01:54AM (#11874547)
I think I can isolate the entire issue to this one line, emphasis mine:

> Only a small percentage (6.1%-16.7%) of configuration parameters are set by the majority of users; a significant percentage (up to 54.1%) of parameters are rarely set by any user.

The necessary question is, how many installations used at least one rarely-set parameter? Would those installations have happened without that parameter? How much effort went into developing that parameter, versus the profits of those installations?

Re:Too Many Knobs by Negitivefrags on Friday June 10, 2016 @02:47AM (#11874680)
Reminds me of this article: http://www.joelonsoftware.com/articles/fog0000000020.html

The pull out quote being:

A lot of software developers are seduced by the old "80/20" rule. It seems to make a lot of sense: 80% of the people use 20% of the features. So you convince yourself that you only need to implement 20% of the features, and you can still sell 80% as many copies.

Unfortunately, it's never the same 20%. Everybody uses a different set of features.

Re:Too Many Knobs by felipeerias on Friday June 10, 2016 @06:46AM (#11875463)
The same idea applies to those advocating for having "simple" and "expert" configuration menus: everybody's expertise is different, and changes over time as we learn and forget things.
Re:Too Many Knobs by rasz_pl on Friday June 10, 2016 @02:15PM (#11878586)
Plus there are power users and sheep. Sheep will follow power users, power users will expect extra features. No configurability means no power users means no sheep.
Re:Too Many Knobs by afro88 on Friday June 10, 2016 @06:24AM (#11875398)
Right - just because I rarely change a parameter doesn't mean it's not important. In fact, some of the most important parameters are set once and then forgotten about.
Re:Too Many Knobs by tehrei on Friday June 10, 2016 @06:30AM (#11875417)
Like, say, IFS in bash. Have you ever needed to set IFS? Do you know what it does? I've set it maybe 5 times and practically each one was to $'\n' so I can read newline-delimited input values in a while loop. But I appreciate the fact that I can set it to literally anything, if I ever need to.
Re:Too Many Knobs by JoshTriplett on Friday June 10, 2016 @02:55PM (#11878946)
> I've set it maybe 5 times and practically each one was to $'\n' so I can read newline-delimited input values in a while loop.

Does "| while read line" not do what you want here?

Re:Too Many Knobs by sopooneo on Friday June 10, 2016 @10:42AM (#11876664)
Also, until you have lots of users, how can you guess which 6.1%-16.7% of parameters most of them will use?
Re:Too Many Knobs by ball_of_lint on Friday June 10, 2016 @03:00PM (#11879006)
This makes me think of a cached model of settings: Most used can be configured in-app Less used need to edit the config Least used need to be set at build/install