Evidence Surfaces That MS Violated 2002 Judgement
whoever57 writes "In the Comes Vs. Microsoft case, the plaintiffs believe they have found evidence that Microsoft has failed to fully disclose APIs to competitors. If true, this would mean that Microsoft has violated the 2002 judgement. This information has become available since the plaintiffs have obtained an order allowing them to disclose Microsoft's alleged misbehavior to the DOJ ('appropriate enforcement and compliance authorities')."
A business this big doesn't need time to change - it needs desire to change. With all its (possible) evil implications, European Union seems to give Microsoft a desire to change.
If the allegations are true, and it turns out that MS might somehow not be the shining beacon of Justice and Honour that we've come to regard it as (okay, I'll cut the sarcasm now), what is the worst that will happen to MS? And are they really concerned...ever?
I'd rather we skip the monetary fines that are becoming meaningless and go for revocation of patents. Can you imagine if MS had it's patents revoked and switched to a free-for-all? That would be nice... Ah, to dream.
It doesn't surprise me, but not for the reasons you might think.
There's a difference between APIs internal to the operating system, and APIs intended to provide a userland interface. If Microsoft userland products are using the internal APIs, then those APIs ought to be released. Otherwise, I don't see the probelem.
I'm no Microsoft apologist, but I'd be interested to see which APIs are being discussed here before I go off on an anti-Microsoft rant.
tasks(723) drafts(105) languages(484) examples(29106)
There's a difference between APIs internal to the operating system, and APIs intended to provide a userland interface. If Microsoft userland products are using the internal APIs, then those APIs ought to be released. Otherwise, I don't see the probelem.
I think you're considering this a little too much from the programmer's point of view and not enough from the legal/economic point of view. The real distinction that needs to be determined is which APIs are being used by MS in conjunction with some offering that competes in a separate, existing market. For example, APIs that interoperate with MS's Web browser, virus detection, and allow for communication with their server offerings may be categorized as internal to the operating system, but they provide functionality for bundling and tying from an economic point of view.
Don't worry, even not knowing what APIs are being discussed we can always go off on anti-microsoft rants on other topics. That's the fun of it, they're doing so many things that are unethical and criminal that there is always something to rant about.
I'd love to believe this. But I don't recall anything of the sort happening when MS showed a deliberately fabricated video (of Win98 crippled by the removal of IE) in court during the antitrust trial.
"One processor architecture (x86) is better than four completely different"
Not at all. If there were lots and lots of CPU architectures, OS's would have to be written to run or be ported easily to another processor architecture. This would open up competition to the "best" processor, rather than the best implementation of the X86 command line.
It probably would have forced OS vendor to be far more innovative in terms of virtualization and other technologies that we can't even dream of.
You were mistaken. Which is odd, since memory shouldn't be a problem for you