mitch074
Splendid
About the ballot screen: this allows one to download and install whatever browser one's favourite, without having to pass through the "Run IE, get infected" spot. One can even (gasp) choose not to get a browser! Like, a browser is sooo useful on a server... Like, say, a media/streaming server.
About MacOS X/Linux not getting hit with this: Safari can be removed from OS X. A base Linux install doesn't even include a GUI - much less a browser. And this is irrelevant anyway, since neither are convicted monopolists (and MS was asked to solve the monopoly abuse of forcing a browser on all Windows users).
About Firefox/Chrome/whatever starting faster than IE; it depends on:
- the machine: due to Firefox using a third of the RAM IE uses, on machines with low RAM, Firefox starts MUCH faster; so does Chrome (although Chrome can end up using more RAM than IE due to its use of sandboxed separate processes)
- what you do with it: since IE 8 has to restart a separate thread for each tab it opens, including a separate thread for each plugin it loads, opening a tab in IE can take as much as 5 seconds before it becomes responsive (dixit IEblog)
- how you load it: since IE is heavily integrated with Windows Explorer, most of it is preloaded when Windows starts (a great chunk of the chrome, the HTML and Jscript engines) so that all that's left to do is populate history and favourites menus, and preload ActiveX controls on browser first start (this is also why you can hang Windows Explorer if IE crashes - yes, even IE 8); a workaround is to allow each Windows Explorer sessions to start in different threads, but this results in even more RAM consumption
About MacOS X/Linux not getting hit with this: Safari can be removed from OS X. A base Linux install doesn't even include a GUI - much less a browser. And this is irrelevant anyway, since neither are convicted monopolists (and MS was asked to solve the monopoly abuse of forcing a browser on all Windows users).
About Firefox/Chrome/whatever starting faster than IE; it depends on:
- the machine: due to Firefox using a third of the RAM IE uses, on machines with low RAM, Firefox starts MUCH faster; so does Chrome (although Chrome can end up using more RAM than IE due to its use of sandboxed separate processes)
- what you do with it: since IE 8 has to restart a separate thread for each tab it opens, including a separate thread for each plugin it loads, opening a tab in IE can take as much as 5 seconds before it becomes responsive (dixit IEblog)
- how you load it: since IE is heavily integrated with Windows Explorer, most of it is preloaded when Windows starts (a great chunk of the chrome, the HTML and Jscript engines) so that all that's left to do is populate history and favourites menus, and preload ActiveX controls on browser first start (this is also why you can hang Windows Explorer if IE crashes - yes, even IE 8); a workaround is to allow each Windows Explorer sessions to start in different threads, but this results in even more RAM consumption