No, Google is not making the Android SDK proprietary. What’s the fuss about?
|
|
|
Comments (1)
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

sure the source for the SDK may be under the apache license, but if i ever accept the binary license then i am barred from distributing, participating in the creation of, or promoting in any way a software development kit derived from the SDK, which at this point i'd have to be doing if i wanted to use the SDK source. because i can't see how i'd avoid sending in bugreports or mention the fact that i am using an SDK built from source.
a non-free binary license is in a way similar to redhat vs centos. only that redhat does not prevent its clients from distributing, participating in the creation of, or promoting in any way a linux distribution derived from redhat enterprise linux.
redhat got a lot of flack for their binary license and it took a long time for the community to realize that redhat is not going to go after centos.
but i can't see google having the same reaction against a competing build of the android SDK because such an SDK would undermine what they are trying to achieve with that anti-fragmentation clause.
greetings, eMBee.