MSE is a much better solution than Norton, barely any dialogs except when malicious code is detected. GC might slow down the computer a notch, but memory leaks

MSE is a much better solution than Norton, barely any dialogs except when malicious code is detected. GC might slow down the computer a notch, but memory leaks are way too common in frameworks that don't use GC. This is not to say that systems with GC would have zero memory leaks, but it definitely helps. >I don't think of this as a freedom/monopoly thing. This is a display/gui/responsiveness architectural issues. There are simply things you can do now on Windows that you can't do on the web, and windows needs to give the user more control and restrict the types of interactions developers can have with the user if it wants to solve this problem. Web developers have been living with these guidelines for a long time. It's nothing new or onerous. After all, if we're not in this for the users, what the heck are we doing? For example, how would your proposed method restrict iTunes(which installs a whole bunch of services, startup items, etc. and tries to trick the user into installing Safari). How will this affect legacy apps? The only real solution is to move to a restrictive approval process like the App store.