Let me explain something to you.
When you add features and configurability to a system, you have to decide where to put them. In other words, if you're going to provide Feature X and allow users to configure Feature X, you have to provide controls for it somewhere. Do this often enough and the number of controls and options gets to be a bit unwieldy. At that point usually somebody has the bright idea of just adding an "Advanced" panel on the configuration, and sticking all the extra options in it (or an "Advanced" sub-menu off the main menu), but there are two problems with this:
\r\n\r\n
\r\n- It doesn't address the root problem (too many features and options to manage) and, inevitably,
\r\n- The "Advanced" panel/menu becomes hopelessly cluttered.
\r\n
\r\n\r\n
When you reach this point you have to step back and evaluate your feature set, and ask yourself: what do we really need? Anything you can't justify based on significant demand and significant usage should go. And anything that confuses more people than it helps should go. Firefox did it, GNOME's doing it. It's a fact of development that can't be avoided, and you can complain about "dumbing down" all you like without changing it.
