5 ms·
> The biggest problem I have with IE is disjointed updates. They don't care enough to fix the one thing they need to fix. And don't tell me they're doing automa
by smacktoward 13y ago
> The biggest problem I have with IE is disjointed updates. They don't care enough to fix the one thing they need to fix. And don't tell me they're doing automatic updates now, they need to go back and fix all versions. Including on Windows XP.
Their claim is that it's impossible to provide modern IE for older versions of Windows, because IE is so deeply tied into the OS it requires features and libraries that are intimately tied to newer versions and don't/can't exist on (say) XP.
(Not saying I endorse that as a reasonable position, just explaining why they do things the way they do.)
- bcoates 13y agoI thought that the claim was the XP and Vista are no longer supported versions and nobody need write new software for them.
- yuhong 13y agoNo longer in mainstream support.
- wslh 13y agoTheir claim is that it's impossible to provide modern IE for older versions of Windows, because IE is so deeply tied into the OS it requires features and libraries that are intimately tied to newer versions and don't/can't exist on (say) XP. 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.
- ryankshaw 13y agoSo 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.
- untog 13y agoInteresting to note that Apple does the same thing with Safari.
- protonfish 13y agoThat's not a reason - it's an excuse. Every other major browser works fine across Windows versions and MS claims they can't? It's a marketing decision. Microsoft is an OS company so tying their latest and greatest browser to an OS upgrade is compelling.
- wmf 13y agoSupposedly the performance in IE 10/11 comes from not having XP compatibility layers.
- smacktoward 13y agoThe question of how intimately Windows and IE are tied together is a longstanding one, and in fact was a central issue in the antitrust case against MS (http://en.wikipedia.org/wiki/United_States_v._Microsoft_Corp. http://en.wikipedia.org/wiki/United_States_v._Microsoft_Corp...). The question was discussed at length in Judge Thomas Penfield Jackson's findings of fact (http://www.justice.gov/atr/cases/f3800/msjudgex.htm http://www.justice.gov/atr/cases/f3800/msjudgex.htm): In contrast to other operating system vendors, Microsoft both refused to license its operating system without a browser and imposed restrictions — at first contractual and later technical — on OEMs' and end users' ability to remove its browser from its operating system. As its internal contemporaneous documents and licensing practices reveal, Microsoft decided to bind Internet Explorer to Windows in order to prevent Navigator from weakening the applications barrier to entry, rather than for any pro-competitive purpose... Microsoft's executives believed that the incentives that its contractual restrictions placed on OEMs would not be sufficient in themselves to reverse the direction of Navigator's usage share. Consequently, in late 1995 or early 1996, Microsoft set out to bind Internet Explorer more tightly to Windows 95 as a technical matter. The intent was to make it more difficult for anyone, including systems administrators and users, to remove Internet Explorer from Windows 95 and to simultaneously complicate the experience of using Navigator with Windows 95. As Brad Chase wrote to his superiors near the end of 1995, "We will bind the shell to the Internet Explorer, so that running any other browser is a jolting experience." ... Starting with Windows 95 OSR 2, Microsoft placed many of the routines that are used by Internet Explorer, including browsing-specific routines, into the same files that support the 32-bit Windows APIs. Microsoft's primary motivation for this action was to ensure that the deletion of any file containing browsing-specific routines would also delete vital operating system routines and thus cripple Windows 95. So while it was originally a marketing decision -- the two were tied together specifically to put competitors at a disadvantage -- the implementation of that decision was not just marketing. It was implemented technically too, to the point where removing IE from a copy of Windows would break the OS. So regardless of the motivation behind the decision, the fact remains that the two things are tangled up with each other quite deeply. Microsoft could have gone back at a later point and un-tangled them, but that would have been a huge project, and there was no real motivation for them to do so -- the settlement agreement that ended the antitrust case didn't require them to, and the market wasn't rejecting Windows with IE tied into it. So it stayed tangled up. The big irony is that by tying the OS and browser together to get an advantage over their competitors, they ended up disadvantaging themselves. Those competitors can now turn out new versions of their browsers at a fast clip, because they're not tied to any release schedule other than their own. IE is tied to Windows' release schedule, however, so it improves at a glacial pace compared to other browsers, making it less competitive over time.