3 ms·
what's funny is that most people think of that trial as being about Microsoft "putting IE in the operating system". Which is hilarious, because where else is y
by dekhn 4y ago
what's funny is that most people think of that trial as being about Microsoft "putting IE in the operating system". Which is hilarious, because where else is your core HTTP fetching DLL, your core HTML parsing DLL, etc, going to go otherwise? A Chromebook is basically an operating system running Chrome and more or less nothing else, vindicating Microsoft's technical decision.
- bb88 4y agoMicrosoft's claim at the time was that IE couldn't be removed from the system because it had been integrated into the OS. The government was able to show otherwise. It really had nothing to do with the architecture, but the legal arguments Microsoft's lawyers were making. But despite that, let's not gloss over about what MS did. If they had been successful there wouldn't have been one web, there would have been two: One for MS (ActiveX and proprietary MS extensions) and one for MacOS/Linux/Netscape/Mozilla/Opera etc. This would have been part of their "Embrace/Extend/Extinguish" strategy they were known for at the time.
- dekhn 4y agoNo, the government didn't show otherwise (in my opinion). They showed you could remove the component, but it degraded essential functionality because IE and the components (HTTP, HTML and form display) depended on the (the OS did, for updates and other applications). I mean the IE the software component, not the browser, because MSFT comingled them at the OS level. At the time, they planned on replacing much of the user interface with web controls, and even today you can see many vestiges of Internet Explorer-like behavior even though IE is gone. i woudl have agreed with you in the past but when I was curous and went back through all the cases I was surprised to see that I think (from a technical perspective) MSFT was completely right to do what they want, and the main issue was that they simply didn't understand how to win a case in court.
- josefx 4y ago> Which is hilarious, because where else is your core HTTP fetching DLL, your core HTML parsing DLL, etc, going to go otherwise? Microsoft insisted that the OS needed the internet explorer executable, not only the rendering engine components. You couldn't even run windows update without it opening IE - in order to load a native ActiveX component that then performed the work. They where desperate to make everything depend on IE without a plan of how to make good use of it, which shouldn't be surprising, back then any complex use of IE would have blue screened the entire system. > vindicating Microsoft's technical decision. Imagine a ChromeOS based on IE5 and tell me why I shouldn't break down in hysterical laughter just thinking about it.
- dekhn 4y agoIt makes perfect sense to me that if MSFT made IE a necessary component to upgrade the operating system, then insisting the OS needs that executable is an absolutely (technically) correct thing to say. I said it vindicating their decision- not that IE was a good foundation to build a presentation layer on.
- josefx 4y ago> if MSFT made IE a necessary component to upgrade the operating system, > then insisting the OS Arguing that a change that had no technical merit made IE necessary, when you are under scrunity for abusing your market position to push IE, seems kinda counterproductive. > I said it vindicating their decision- not that IE was a good foundation to build a presentation layer on. Then how does chrome OS vindicate them? You obviously agree that IE was not fit for that purpose.