Live data from Hacker News

Google’s iron grip on Android: Controlling open source by any means necessary

arstechnica.com

61–70 of 234 posts

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#61

> Google was terrified that Apple would end up ruling the mobile space. So, to help in the fight against the iPhone at a time when Google had no mobile foothold whatsoever, it was decided that Google would buy Android. And Android would be open source. This is blatantly false. Google bought Android in 2005, two years before the iPhone was announced.

Android clearly went in a different direction post-iPhone.

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#63
post #46

Earlier quoted context omitted.

> Google is stuck behind a rock and a hard place. If they don't try to create incentives for a unified experience, they get bashed for encouraging fragmentation, if they do assert a level of control, they get bashed for not being completely open. This is exactly the position Microsoft was in during the mid-1990s, even before they went after Netscape. The article is saying that Google is even applying some of the same…

I don't think Apple will be a good defense if Android's market share is 80%.

Hasn't that always been the relationship between Microsoft and Apple in the desktop world?

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#64

Most of the examples of Google closed apps that are not part of the AOSP release are in fact apps that are based off of Google data-center services. Would it really help Samsung if the source to the Gmail app was open? Since Google controls the server side, and the client-server protocol, it limits the amount of innovation they can do. The web equivalent would be like claiming that Chrome OS isn't open because the so…

> Google is stuck behind a rock and a hard place. If they don't try to create incentives for a unified experience, they get bashed for encouraging fragmentation, if they do assert a level of control, they get bashed for not being completely open. This is exactly the position Microsoft was in during the mid-1990s, even before they went after Netscape. The article is saying that Google is even applying some of the same…

I read the article and kept hearing echos of the Microsoft strategy of the 90s as well.

History may not repeat, but it rhymes.

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#65

"In an ocean with great waves, whales fly into the air unnoticed, but in a calm pond, even the tiniest minnow makes a ripple." -confucius When the iPhone debuted, no doubt Google sensed the impact, and Apple's ability to create an effective closed ecosystem had already been proven with iTunes. I believe that Google wanted to undermine the market long enough to understand it. True enough, "android winning" was not the…

> I believe that for Google, Android started as a strategy in search of a goal. It was a smokescreen to prevent Apple from taking a dominant position by default

Impossible. Google bought Android years before Apple sold a single phone.

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#66
post #33

I think alot of people misunderstand what open source means. It's nothing more than allowing people to see the source code, and use it (including forking). Open source doesn't require you to cooperate with anyone, it doesn't require you to give away access to APIs, it doesn't require you to do anything beyond whatever is explicitly stated in the license. Google, Canonical, Oracle, IBM, Red Hat, SUSE, etc... aren't re…

Well, there is a philosophy (or rather, various different philosophies) that go along with the legal structures, and different projects have different levels of adherence to those ideas. It eventually comes down to perception of value. Part of the original attraction of Android was its openness, if Google is now closing off substantial functionality, to head off competition, then it's not unfair for people to re-eval…

> Part of the original attraction of Android was its openness, if Google is now closing off substantial functionality, to head off competition, then it's not unfair for people to re-evaluate their enthusiasm for the product.

Very well put! Its not a legal perception that theres something wrong about what they are doing(and nobody are saying that they cannot do it in the legal aspect).. its a betrayal of some part that make people defend android for what it is, a open source project.. its the ideal behind the project that is being broken

If its not like that anymore, the same people that support it for its openess should be aware of it.. and see that things are actually, gradually and silently changing..

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#68

So, every Samsung phone effectively comes with three versions of the main apps - the AOSP version, the Google Play version, and Samsung's bloatware? This seems like a terrible situation for users. Can someone with a Samsung smartphone confirm this? If this is the case, how are the apps organized when you first buy the phone - are they all in one big apps list?

Samsung devices ship with two versions, remember that while Samsung can't opt out of the Google apps, they're free to remove any AOSP app they'd like.

In fact, I've had AOSP apps disappear from my Cyanogen Mod ROM when I installed gapps, although I don't know if that was due to being overwritten or just part of the install script.

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#69
post #3

Correct me if I'm wrong, but isn't Linus Torvalds famous for his iron grip of Linux? In a very different way, to be sure, but it's my understanding that just because you make something open source doesn't mean you have to (or even should) relinquish control. I think it's also pretty standard to open-source the core and keep the baubles proprietary. GitHub, for example, made their git interaction library open-source b…

Every open source project has someone (or some group) in control, and contributions can't land without their say so. But anyone who feels that the current leadership is doing it wrong can fork the code and try to persuade people to use their version. This is very important to the way open source software works. Google have a level of control beyond that: they undermine anyone trying to fork Android by not letting the…

Sure. That makes perfect sense to me - Google apps and services aren't open source in spirit or practice. If I wanted a pure open-source mobile OS of my own, I wouldn't want any of Google's apps or services tainting it; if I did, Google would evaluate that option on their own, as they should.

Re: Google’s iron grip on Android: Controlling open source by any means necessary

#70
post #46

Earlier quoted context omitted.

I don't think Apple will be a good defense if Android's market share is 80%.

80% does not a monopoly make. Microsoft was in an entirely different position at the time.

Percentage of market share is not a clear indication of monopoly. From what I could find, 50% is typically the bare minimum to warrant consideration, and 70 - 75% will get more serious scrutiny. Also, it differs from country to country. In the UK, Tesco was investigated even though it had a market share of only 30%.

I also recall reading one of the EU's regulators (was it Joaquin Almunia?) say that (paraphrasing) "we start sniffing around when any one party gets a market share north of 60%." Unfortunately, I cannot find that article.

Post reply on HN