News for hackers. Stuff that matters.
Re:Google’s iron grip on Android: Controlling open source by... by parennoob on Sunday October 20, 2013 @10:28PM (#6582848)
When someone like Github does this (make some parts of their code open-source, but others closed-source), journalists don't write critical pieces about them, do they? I mean, Google leaves a bad taste in my mouth since they started shuttering services like it was Christmas at the Google Service Chopping Block, but I don't see them being actively evil here.

It's all according to the previously openly aired plan. Google keeps all of the existing code open source. Anyone who wants to build a fork can do so. Now if they want a hardware platform to run on, go find one outside the Open Handset Alliance ecosystem. It's fair game -- if a hardware partner thinks that one of Google's competitors can provide a better Android fork, they are free to leave the Alliance and go partner with that competitor. They will still get an enormous amount of code for free in AOSP. They just won't get all of the services that Google is building specifically for its own version of Android. How is any of this maintaining an "iron grip" in any way? Just contrast this with Apple where it is the sole owner of everything to do with the OS and app marketplace.

Re:Google’s iron grip on Android: Controlling open source by... by pavanky on Sunday October 20, 2013 @11:47PM (#6583204)
> Anyone who wants to build a fork can do so. Now if they want a hardware platform to run on, go find one outside the Open Handset Alliance ecosystem. It's fair game -- if a hardware partner thinks that one of Google's competitors can provide a better Android fork, they are free to leave the Alliance and go partner with that competitor.

A good example of this is Amazon. They are doing this successfully.

Re:Google’s iron grip on Android: Controlling open source by... by aray on Monday October 21, 2013 @04:08AM (#6584056)
Another example is OUYA.
Re:Google’s iron grip on Android: Controlling open source by... by tapsboy on Friday November 01, 2013 @01:27AM (#6651962)
And Aliyun OS And Baidu Yi May be even the newly funded CyanogenMod company
Re:Google’s iron grip on Android: Controlling open source by... by apetrovic on Monday October 21, 2013 @02:58AM (#6583814)
> Now if they want a hardware platform to run on, go find one outside the Open Handset Alliance ecosystem.

Imagine you want to sell a Linux laptop with your own Linux distribution. You're just a small shop in California, and you're shopping around to find a manufacturer for your laptops. And you find that anyone connected to Microsoft (Foxconn, Asus, Acer, Gigabyte, etc) can't do any job with you. Would you say "that's fair, Microsoft isn't evil by forcing hardware manufacturers to work exclusively with them" in such situation?

Re:Google’s iron grip on Android: Controlling open source by... by icebraining on Monday October 21, 2013 @11:05AM (#6585995)
That's not what they're doing. HTC, Samsung, etc still sell non-Google OSs, like Windows Phone and Bada.

A good analogy would be Microsoft preventing you from selling your fork of Windows on those manufacturers, which happens to be exactly what every big OS maker does, by simply not distributing it under a Free license.

Re:Google’s iron grip on Android: Controlling open source by... by zobzu on Sunday October 20, 2013 @11:06PM (#6583027)
AOSP is so open that the previous AOSP leader at Google quitted over the lack of openeness.
Re:Google’s iron grip on Android: Controlling open source by... by tomkarlo on Sunday October 20, 2013 @11:20PM (#6583081)
That's a mischaracterization of his own comments on why he left. It had to do with open sourcing GPU drivers, which is probably an issue with other vendors, not Google.

See: https://plus.google.com/112218872649456413744/posts/9HHRURor...

Re:Google’s iron grip on Android: Controlling open source by... by throwaway2048 on Monday October 21, 2013 @05:37AM (#6584395)
It was Google's choice to put that hardware into the phone, and it was their choice not to pressure qualcomm into being more open.

Your argument itself is also somewhat of a mischaracterization, because at least Google could have wrestled redistribution rights for the binary drivers, thus making AOSP actually usable on the nexus, and they didn't even bother with that.

Vendors are a convenient whipping boy when don't care about openness but wanna look like you do.

Re:Google’s iron grip on Android: Controlling open source by... by fpgeek on Monday October 21, 2013 @07:46AM (#6584814)
There's a very, very simple problem with your argument:

https://developers.google.com/android/nexus/drivers#razor

Re:Google’s iron grip on Android: Controlling open source by... by throwaway2048 on Monday October 21, 2013 @03:03PM (#6587519)
and here is the problem with yours, from the EULA:

     Subject to the terms of this Agreement, Licensor hereby grants to
     You, free of charge, a non-exclusive, non-sublicensable,
     non-transferable, limited copyright license, during the term of
     this Agreement, to download, install and use the Software
     internally in machine-readable (i.e., object code) form and the
     Documentation for non-commercial use on an Authorized Android
     Enabled Device and non-commercial redistribution for academic
     purposes only of a reasonable number of copies of the Authorized
     Android Enabled Device Software (the "Limited Purpose"). You may
     grant your end users the right to use the Software for
     non-commercial purposes on an Authorized Android Enabled Device.
     The license to the Software granted to You hereunder is solely for
     the Limited Purpose set forth in this section, and the Software
This makes it entirely impossible for AOSP to distribute the drivers
Re:Google’s iron grip on Android: Controlling open source by... by zobzu on Monday October 21, 2013 @04:21AM (#6584099)
well actually while I get where you're coming from, that's still correct. if AOSP was more open he wouldn't have left. Google doesn't give a damn about openness right now.
Re:Google’s iron grip on Android: Controlling open source by... by tomkarlo on Monday October 21, 2013 @08:17AM (#6584953)
"If AOSP were more open he wouldn't have left." Can you substantiate that statement at all? AOSP's "openness" is determined by its licensing, which is a standard Apache 2.0 license. The issue was whether certain vendors would contribute to AOSP under that license, not whether AOSP was open enough.
Re:Google’s iron grip on Android: Controlling open source by... by voltagex_ on Monday October 21, 2013 @02:34AM (#6583742)
Blame mobile chipset vendors for that one.
Re:Google’s iron grip on Android: Controlling open source by... by rsynnott on Monday October 21, 2013 @07:57AM (#6584859)
> When someone like Github does this (make some parts of their code open-source, but others closed-source), journalists don't write critical pieces about them, do they?

Github don't constantly go on about how 'open' Github is, though.

Re:Google’s iron grip on Android: Controlling open source by... by parennoob on Monday October 21, 2013 @03:41PM (#6587735)
True, but Github does use the halo of "Open Source" a lot to promote themselves (or others promote them using it..e.g. http://www.wired.com/opinion/2013/03/github/) while overlooking the fact that most of their codebase is very close sourced indeed.
Re:Google’s iron grip on Android: Controlling open source by... by demallien on Monday October 21, 2013 @01:36AM (#6583560)
Anyone who wants to build a fork can do so

Not really. You will have your mainline Abdroid implementation shutdown if you do this. Google is clearly doing this to make forking a very risky proposition for device manufacturers. It's the antithesis to open.

Re:Google’s iron grip on Android: Controlling open source by... by gibwell on Monday October 21, 2013 @01:19AM (#6583513)
Google used 'Android is open' as a dishonest slogan to convince developers that it wasn't just a power play.

That is why they are being criticized. It's not about who is more open. It's that Google misled everyone about their intentions.

Re:Google’s iron grip on Android: Controlling open source by... by afsina on Monday October 21, 2013 @03:14AM (#6583871)
Prove that Android is not open.
Re:Google’s iron grip on Android: Controlling open source by... by devcpp on Monday October 21, 2013 @06:43AM (#6584573)
He meant free (as in freedom), not open. "Proof" of that is in the submission's article. It's not exactly a formal proof but it has convinced most people here.

Unfortunately, this highlights some weaknesses in the GPLv2, which is supposed to guarantee freedom.

Re:Google’s iron grip on Android: Controlling open source by... by rsynnott on Monday October 21, 2013 @07:58AM (#6584863)
Android largely isn't GPLv2.