|
> but I don't see why the browser is singled out as something needing special legal treatment Does your calculator interact with anything else but your computer? Same with file manager (SMB excluded)? Now lets look at the browser, it interacts with different servers, via the HTTP protocol, and the documents they serve via many different technologies such as HTML, Javascript, Java, XML, Flash, along with others. 'Back in the day' Microsoft did a very strong push to tie IE in with Windows, then push developers to use ActiveX on websites so they would only work with Microsoft products. There was no HTML5 multi-platform interoperability, if you wanted to visit a huge number of sites (many government ones too), you used Windows on X86, and you used IE. Even worse, after the early versions of IE, they dug its hooks deep in to the operating system so it became WindowsIE, you didn't have one without the other. |
I could argue that the TCP/IP stack is "bundled" with the operating system, and it's something that's very difficult to change (if not impossible without recompiling the kernel). Network engineers have probably had to put up with different TCP/IP stacks using different congestion control algorithms, impacting fairness of bandwidth usage on their networks. So by the same pretense, shouldn't TCP/IP stacks require the same choice that Microsoft were required to offer with browsers?