[roberthahn]

The testing that would be required to support toggles would be for 2^n. I’m not sure that’s a good solution.

[wavemode]

> The testing that would be required to support toggles would be for 2^n

I don't think that's really true, unless the behavior of each toggle is tightly coupled to the behavior each other toggle.

Case in point - most mature apps nowadays do have hundreds of toggles for various settings and features.

[dlcarrier]

Makes me wish more apps followed the UNIX model of separating every feature into separate applications with well documented interfaces that only change when new features absolutely require it and otherwise are only updated for security patches.

[roberthahn]

Yeah I like that idea too. Theres a lot of people who would have trouble with that approach though.

[AlienRobot]

One common case I notice this is with FFMPEG. Everything that saves a video needs its own dialog with different settings. It would make a lot more sense if you had 1 single polished FFMPEG frontend that everyone just streamed data to.

On the other hand, I'm afraid that if this did happen that FFMPEG frontend would look like a GNOME app and I would hate using it.