decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Which Microsoft are we talking about? | 80 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Which Microsoft are we talking about?
Authored by: Anonymous on Monday, June 03 2013 @ 10:52 AM EDT
If Microsoft was concerned that their image MIGHT be
tarnished by seeming like they want everything to be
completely proprietary and owned by them, they're a few
decades late.

Microsoft has ALWAYS been "all our stuff, all our tools, all
the time." Microsoft has NEVER been a fan of
interoperability. They're the guys who created the doctrine
of "Embrace, Extend, Extinguish" to try and wrest control of
the HTML spec from W3C. They effectively killed true open
XML documents by packing standards bodies to weasel in
proprietary extensions to protect their closed ownership.
You're thinking an AMICUS BRIEF is the thing that's going to
give people a bad taste in their mouth?

Heck, as the article Google quoted pointed out, Java was a
reaction against "you always need to cut a check to
Microsoft." The score's been known for a good long while.

And, frankly, MS has more to lose here than Oracle.
Oracle's trying to extend it's ownership of Java to new
markets - it's speculative revenue. They made no money from
Java before. They'd like a new business where mobile
operators give them money. Microsoft is in a different
place. Microsoft has an existing, huge business around the
closed nature of the .Net languages today.

If a court rules affirmatively that anyone can always re-
implement an API, it hurts Oracle by them not getting new
dollars, but it hurts Microsoft because it cuts into
Microsoft's existing revenue stream. Anyone interested
could freely re-implement .Net compilers that could directly
compete with Microsoft's, and Microsoft would be powerless
to stop them.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )