3 ms·
I've heard that, but no one is forcing them to program it that way. They could do the equivalent of static linking and include the necessary components in the
by ars 11y ago
I've heard that, but no one is forcing them to program it that way.
They could do the equivalent of static linking and include the necessary components in the browser instead of the OS.
That's more or less what the Utilu IE Collection does I think.
- netheril96 11y agoYeah, they could do that now, but that doesn't help the IE 6, 7, 8 problems, does that?
- lmm 11y agoYes it does. They could ship a statically-linked copy of Edge to Windows Vista (and even XP) users via Windows Update. The old IE DLLs would have to stay there to be used by the system, but the actual web browser could be a newer one.
- chris_wot 11y agoThat's a terrible idea from a security standpoint.
- lmm 11y agoIf they're stopping delivering security updates for those versions of IE then it's better than nothing. Actually assuming they keep the statically linked Edge updated via windows update then I don't see any issues (as annoying as a large update to a statically linked program will be).
- Kwpolska 11y agoMicrosoft Edge is a Universal Windows App, i.e. uses APIs that exist on Windows 10 only. And Microsoft is not backporting that.
- pjc50 11y agoIt's the other way round: programs include the browser as a COM component. https://msdn.microsoft.com/en-us/library/aa752040%28VS.85%29.aspx https://msdn.microsoft.com/en-us/library/aa752040%28VS.85%29... So on the older operating systems, programs that shipped with the OS will be embedding the browser as a COM component, usually for help purposes. If they're rendering local HTML (or generated HTML!) then they require that to keep working. So that particular interface has to be maintained, making it very difficult to upgrade. Microsoft were kind of correct in the "browser choice" lawsuit that they'd used the browser as an OS component, and everyone else was correct that this was kind of a bad idea. On the other hand, how do you embed a browser component in a forward-compatible way?
- nitrogen 11y agoOn the other hand, how do you embed a browser component in a forward-compatible way? Use a consistent API and just upgrade the rendering engine, while maintaining quirks mode. It's not as much of a problem anymore because HTML5 specifies consistent parsing and rendering behavior for new and old documents.
- Dylan16807 11y agoEmbedded rendering of local HTML doesn't need security updates, so that's not a major problem. You can leave it alone while you update the actual browser.
- scholia 11y ago> Microsoft were kind of correct in the "browser choice" lawsuit that they'd used the browser as an OS component, and everyone else was correct that this was kind of a bad idea. Unfortunately, Microsoft signed a consent decree with the DoJ in 1995 which allowed them to add features to the operating system but meant they couldn't tie a separate program to the operating system. Therefore the browser had to be an added feature. This was only a tiny part of a much broader decree. None the less, you can thank Janet Reno and the US government for the problems this has caused ever since ;-)
- pjc50 11y ago