6 ms·
So why not un-tie it from the OS? If Chrome, FF, & Safari can do all that they do without deep os integration, why not IE? someone said "One of the core reason
by ryankshaw 13y ago
So why not un-tie it from the OS? If Chrome, FF, & Safari can do all that they do without deep os integration, why not IE? someone said "One of the core reasons is that new IEs uses security support from the OS, like low privileges, that didn't exist in old Windows OSES" well I don't believe IE11 is any more secure than chrome or firefox, and they don't need that so why does IE?
I know the business model used to be "release a new version of IE, make compatible for only the new version of windows, force everyone to buy a new windows license." and that worked back when there was no competition. but trying to do that in todays market means most savvy users will just use a browser that updates without needing an OS update (or any user action, for that matter).
Really, why doesn't IE just start doing an iterative auto-release cycle like ff or chrome?
- yuhong 13y agoThe problem is dependency on DirectWrite/Direct2D etc that any app can depend on.
- modarts 13y agoCorporate customers who have their shitty intranet apps tied to a specific version of IE for one.
- bcoates 13y agoBecause the availability of IE is part of the Windows platform -- a Windows program gets to assume that IE is installed and the various APIs provided by IE are available. If Microsoft wants older Windows software to work, it has to ensure that when an app written against IE4 invokes the WebBrowser control in IE11 it still behaves as expected. IE doesn't need Windows so much as Windows needs IE.
- leokun 13y agoOS X solves that by using a separate version of Webkit for their webviews that's independent from Safari.
- AaronFriel 13y agoThis is also the case in Windows (now) but only for Metro style applications. Those compiled for Windows 8 use the IE10 control and for 8.1, the IE11 control.