|
|
|
|
|
by haberman
4580 days ago
|
|
> Google is certainly throwing their weight around these days, which is precisely why Microsoft was hated in the 90s. Not really. There's nothing intrinsically wrong with "throwing your weight around," as you put it. For example, that's exactly what IBM was doing when they decimated SCO's absurd lawsuit. Microsoft was hated because they aggressively pushed out competitors in dishonest ways, because they intentionally made it difficult to interoperate with their software through proprietary protocols and file formats, and because they attacked open source. Some of your questions directly illustrate why "throwing your weight around" can be a good thing. Did Sun/Oracle accuse Google of "stealing" Java? Yes, but do you really want to live in a world where people can copyright APIs, thereby giving creators of popular APIs a large amount of control over everyone else? I surely don't (and I say this as someone who has dedicated literally years of my life into designing APIs) but Oracle and Microsoft would like that world. I don't "expect" Microsoft to give away anything, but the fact that their business model depends on tightly controlling it makes them an inherently less open source-friendly company than Google. |
|
To me that sounds a lot like "throwing their weight around" :-) As my post hoped to show, Google simply does it in different ways.
Well... if you believe Yelp, the SkyHook lawsuit and various antitrust complaints in the US and EU, "pushing out competitors in dishonest ways" is something Google is doing as well. And we all know how interoperable YouTube is with Windows Phone devices. And we saw how Google pressured OEMs into not supporting competing software (cf SkyHook, Acer).
So maybe not that different after all.
> Some of your questions directly illustrate why "throwing your weight around" can be a good thing.
No doubt Microsoft supporters will say the same thing about Microsoft's antics :-)
> Did Sun/Oracle accuse Google of "stealing" Java? Yes, but do you really want to live in a world where people can copyright APIs, thereby giving creators of popular APIs a large amount of control over everyone else?
Well, that's the purpose of IP, isn't it? If you create something popular that others find very useful, you deserve enough control to ensure proper compensation.
Otherwise you get what Google did to Sun. Sun sank millions in developing -- and billions in marketing -- Java to make it the dominant development language that it is and to create, out of nothing, a huge Java-savvy workforce. Google, to bring developers to their new platform, simply hijacked the ecosystem with nothing in return to Sun (now Oracle). Of course, Sun was very careless in its control of Java, but I think Google derived immense benefit from Sun's investment and is being extremely selfish in insisting on not respecting their rights.
> I surely don't (and I say this as someone who has dedicated literally years of my life into designing APIs) but Oracle and Microsoft would like that world.
I too have devoted years of my life designing APIs. I see little distinction in the creative effort that goes into either code or API, and I think both deserve equal protection.
In fact, personally, I see Google's world as worse than Oracle/Microsoft's world. Google's arguments in the Oracle case, taken to their logical conclusion, literally remove support for all copyright protection for software. Part of their argument is that APIs are not copyrightable because they're "functional". You know what else is functional? All the code in the world!
But then, Google's software remains locked away in data centers, away from the world's eyes, further protected by trade secret. Of course, it sees no value in other types of protection, only liabilities.
Me, I'd rather live in a world where valuable works cannot be taken without permission, especially since a lot of my work is exposed to the world. I've open sourced a lot of stuff too, but which of my work can be taken freely should always be my decision.
> I don't "expect" Microsoft to give away anything, but the fact that their business model depends on tightly controlling it makes them an inherently less open source-friendly company than Google.
There's nothing intrinsically wrong with being a "less open source-friendly company" either.