Linked by Thom Holwerda on Wed 4th Mar 2009 17:31 UTC, submitted by poundsmack
Permalink for comment 351705
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-02-15
On my network, Internet Explorer is not needed. We use Firefox for web browsing. But even so, we still need to patch and update Internet Explorer to avoid any 3rd party applications that utilize the IE API from potentially causing issues on our systems.
Being able to completely pull out IE and have these apps tap into another browsers interfaces sounds great. This minimizes the complexity and footprint of the installation and minimizes the need to create policies to limit access to Explorer (as its not there, nothing to be concerned with.)
Of course, that would be ideal, but I'd venture to guess there are way too many apps out there that tap into the IE API's and once it is pulled out, there will be a LOT of pressure from other applications to install it so those applications can operate. We'll see.