Linked by Thom Holwerda on Mon 17th Sep 2007 15:17 UTC, submitted by Rahul
Legal Microsoft suffered a stunning defeat on Monday when a European Union court backed a European Commission ruling that the US software giant illegally abused its market power to crush competitors. The European Union's second-highest court dismissed the company's appeal on all substantive points of the 2004 antitrustruling. The court said Microsoft, the world's largest software maker, was unjustified in tying new applications to its Windows operating system in a way that harmed consumer choice. The verdict, which may be appealed only on points of law and not of fact, could force Microsoft to change its business practices.
Permalink for comment 272076
To read all comments associated with this story, please click here.
RE[2]: APIs
by MollyC on Mon 17th Sep 2007 20:01 UTC in reply to "RE: APIs"
MollyC
Member since:
2006-07-04

Actually such HTML-components can easily be replaced by compatible alternatives.

The IE ActiveX Control ought to be removable because there is an alternative with quite some compatibility (Mozilla ActiveX Control).

Rather than relying on a specific HTML-component, the OS ought to have a framework for HTML-components. Think translators or plug-ins. Applications could then use the HTML-widget without having to worry about the actual rendering engine behind the widget, due to the plug-in / translator structure.


--------------------------------------

I agree. In fact, I think we should go back to the days where all OSes had interchangable memory managers available from both 1st and 3rd parties, interchangable task schedulers available from both 1st and 3rd parties, interchangable file systems from 1st and 3rd parties, etc (I guess Linux does do the 3rd of these).

The IE libs are part of the Win32 API that apps rely on, but that doesn't mean that the user shouldn't be able to rip that out and replace it with a dll that supports a clone of that api that purports to do the exact same thing. The user should also be able to rip out the entire GDI subsystem and replace that with a clone api dll. And GDI+. And DirectX. And the HWND api. And all of .NET. And all of OLE too. And WPF. And WCW. Etc.

In fact, I don't think OSes should provide any API at all. Just let the OS provide an api component manager and let the user go out and buy a dlls that support the various APIs that he thinks he might need from third parties and plug them in.

It would suck for programmers that are used to targetting a fixed set of APIs. And it would suck for users that wouldn't have the first clue whom to turn when something goes awry. But I'm sure both programmers and users will adjust and come to appreciate how better off they are under a hodge-podge system.

Oh, but this should only be done for Windows. OSX and the like should still be able to provide a fixed target API for its users and programmers.

Edited 2007-09-17 20:06

Reply Parent Score: -1