The solution of asking users if they want to install these plugins is horrible.
The average user has no idea what a browser plugin is. Adding an option (or even worse another screen in the installer) for this will only result in users accepting the default anyway and also feeling confused/stupid/scared for not understanding it.
This for-nerds-by-nerds hyper-configurable approach is a big waste of time. Normals just want sensible defaults. This is the big idea we're pushing with Ninite and it's frustrating to see someone fail to grasp this so publicly.
Every installer I've used that had any user-friendly implicit settings, also had an "advanced" mode where you could override them, in addition to the button that just installed the software with default settings. Why can't it be put there?
Putting the option in an advanced pane would be as good as not having it. The sort of people who would see it are the same ones that already keep an eye on their browser plugins and uninstall ones they don't like.
I guess my real issue here is that this guy is picking the wrong fight. It's not about consent to install, it's about good or bad software.
Most of the stuff he calls out is probably a win for average users. They can click a link to a song and buy it right away, for example. It's good software.
I get the feeling this guy would be fine with things like the Yahoo or Ask toolbars (bad, horrible, terrible software) because if users stay on their toes while installing stuff they could opt out. Normal people just take the defaults though, and get stuck with a crapped up computer.
Adding choices to the installer feels like the smug, nerdy, you-need-my-help-to-use-computers approach.
While I don't think making installers more complex is the answer, I disagree with your first paragraph. I pay general attention to what installers do but I don't scrounge around my computer looking for changes. I especially don't go to the menus-deep plugin list unless I want to do something like reset flash.
I agree that putting it on the advanced pane would be as good as not having it.
But I disagree that it's good software. Especially in the case of Windows Live, this is Microsoft forcing proprietary extensions in in lieu of actually developing tools for the open web. And in the case of Apple, I think the assumption that people want third-party tools adding hyperlinks to web pages is faulty. Mozilla puts out a solid product, and I haven't heard a lot of people complaining that it needs more tacked-on features.
What it comes down to is that software packages that modify other software packages are bad software. Packages should be self-contained.
The goal of self-contained packages is a good one. I love that this isolation is getting enforced through sandboxing on new platforms like iOS.
Sort of off the main point, but I think Apple's thing just makes it easier for publishers to link into iTunes (those funny phobos.apple links), not rewrite song references it finds or anything like that. Custom protocol handlers like itms:// pop up some terrifying warnings by default and should probably be worked around.
I'd consider plugins that rewrite content as bad software.
What do the Microsoft plugins have to do with developing tools for the open web or not? The plug-ins you're complaining about:
* The Windows Live Sign-in Assistant enables you to automatically sign in to Windows Live websites when you're already signed in with, say, Messenger on your PC, something that's a net win for Messenger users and which really has no web-reasonable implementation. Why is this evil, exactly?
* The Office Live plugin allows users to open documents saved on SkyDrive from their browser in the Office clients. This also works with Office Live Workspaces (for users of that older product) and Sharepoint. Again, why is this evil?
I'm pretty sure that if there were a way to make these things work without needing to use plugins, that's something the team would pursue. But there isn't, so to make the experience of Windows Live and Office users better, these plugins get installed with those products. This seems to be pretty intuitive to me.
There's nothing wrong with plugins. The problem is when I apply a plugin to one package (in these cases the core OS) and it silently adds a plugin to another package.
It's that asking users about something like this is only a solution for the most advanced users and a burden for everyone else. If something is generally useful it should be bundled without question, and if it's junk or obtrusive it should not. This should be judged from the average, non-technical user's perspective.
The average user has no idea what a browser plugin is. Adding an option (or even worse another screen in the installer) for this will only result in users accepting the default anyway and also feeling confused/stupid/scared for not understanding it.
This for-nerds-by-nerds hyper-configurable approach is a big waste of time. Normals just want sensible defaults. This is the big idea we're pushing with Ninite and it's frustrating to see someone fail to grasp this so publicly.