The author has good intentions here but I have to disagree. I don't think that functionality that the browser handles should be moved from the browser's own opt

The author has good intentions here but I have to disagree. I don't think that functionality that the browser handles should be moved from the browser's own options panel to addons, third-party or otherwise. Even if Mozilla themselves offered addons to manage enabling/disabling JavaScript, SSL, certificate management, etc., that gives the impression that they somehow believe that the functionality being moved over to addons is secondary, unimportant, or less of a priority than more simple options which I think is just not true. I'm totally on board with the idea that if less than 2% of users need functionality it shouldn't be placed front and center and maybe it doesn't need to be in the options panel at all but most of his examples aren't the sort of thing I would want removed or outsourced to an addon whether I was a technical user or not. I think the real answer is to prioritize, organize, and simplify. Make the most important, general, and broad options the first ones a user sees. Organize them from most general to more specific (which probably includes an increasing level of complexity as well). Go ahead and hide some of the more fine-grained controls in a panel somewhere that all but those who really know what they're looking for will find it (but make sure to document it, too). Finally, remove anything that simply doesn't need to be there. Those things, I believe, will be very few and far between. The author makes it sound like there are tons of options they could get away with just cutting from the options without anyone noticing but I'm not convinced. Despite the fact that some options are very rarely used, when that rare case of them actually being needed comes up having them available, albeit in some hidden away panel, can make all the difference between a happy and a frustrated user - a user who won't have to go out and search for yet another addon to manage something they thought the browser itself should be able to control. The solution isn't to reduce the number of options, at least not in the way the author promotes. Instead I think it's really just about better organizing and presenting what's already there. Mozilla is all about freedom and their customizability is something a large segment of their userbase loves them for. Why ruin that?