Notably, Moskowitz explained that Firefox -- which you would think would be designed to easily administrate with Group Policy -- cannot be controlled. The reaso

Notably, Moskowitz explained that Firefox -- which you would think would be designed to easily administrate with Group Policy -- cannot be controlled. The reason: "It uses JavaScript files," he says. "There's no Group Policy way, right now, to handle 'odd' file types like .JS or XML files." So it's Mozilla's problem that Microsoft's Policy tools are ridiculously rigid and inflexible? Actually, I don't know anybody who cares if IE wins or loses in the corporate browser world. It's nice to delineate your business/intranet and public/personal activity into other browsers. In fact, to me it's preferable that there's a "legacy" browser to fulfill the web application equivalent of fax-machine duty. I don't envy the work that the IE team has to do to maintain compatibility with ancient and awful applications kludged together for IE 5.5, and I _really_ don't want that stuff in the browser I visit public sites with. As for the set of people that think the power goes from the wall into the "hard drive" and that the internet is a blue "e" icon on the desktop, I stand by a previous comment I made ( http://news.ycombinator.com/item?id=302947 http://news.ycombinator.com/item?id=302947 ), in that I think IE should be vehicle for modern web experience ActiveX controls.