3 ms·

If that is the mentality, then why is android even open source to begin with, after all people can come and "freeload" off AOSP. Google is attempting to gain t

by throwaway2048 13y ago

If that is the mentality, then why is android even open source to begin with, after all people can come and "freeload" off AOSP. Google is attempting to gain the marketing benefits of being "open" while in actuality exerting the same kind of platform level control apple or Microsoft do. You can't have both and really be open. Its the same kind of stupid games Sun played with Java for years.

DannyBee 13y ago
"If that is the mentality, then why is android even open source to begin with, after all people can come and "freeload" off AOSP. " I'm not sure I follow. Freeloading is a huge problem, even in the open source community. This is for example, one of the reasons the GPL exists.
- saurik 13y ago
  Right... which makes the argument then pretty obvious: if freeloading is a serious concern, maybe Android should be released in a way that doesn't allow that (closed, GPL, whatever). You are just being needlessly pedantic if you insist the person you are responding to should have said "under a permissive license that leads to the freeloading problem".
  - DannyBee 13y ago
    Except his complaint was about openness. So exerting control through GPL would be open, but exerting control outside of GPL is not, even if you exert less control and over less people?
    - saurik 13y ago
      ... the comment went so far as to ask why it was open source at all if there was such concern of a freeloading. The fact that it could remain open source and still avoid freeloading just strengthens that argument and undermines your attempt to defend Google's response to the freeloaders. You also brought up the GPL as the open source way to avoid freeloaders, so your new goal of pretending I'm the one claiming GPL would be "open" (especially when I directly compared it to "closed", not "open") seems to be nothing more than trying to hope I'm too stupid to notice. Again: this is a very simple argument: you seem really angry about freeloaders, and yet you chose the license that allows them to exist: as the person you are responding to said, if you care this much, why did you make everything this open? You could have just made it closed source, or you could have used a more closed (yet user-benefiting!) license such as GPL. To be clear: I empathize with your pain (I made similar licensing mistakes a while ago, and ended up with tons of freeloaders), but I can't empathize with your continued complaints and name-calling as if this is something other people did to you :(. As it stands, you have now built a scenario where the people who play along with you (comply with the CTS, get the Google apps, etc.) are handcuffed (making it not exactly "open" anymore for them anyway) and the people who don't (Amazon) are on your "shit list" (leading to any of new SDK-related terms, new closed critical components, temporary closures that aren't "owned up to" as "closed", and when all else fails: bitter tongue lashings on online forums with negative terms like "freeloader" bandied about)... you are trying to have your cake and eat it too, and that's really disingenuous and entirely low of Google.

DannyBee 13y ago

"If that is the mentality, then why is android even open source to begin with, after all people can come and "freeload" off AOSP. " I'm not sure I follow. Freeloading is a huge problem, even in the open source community. This is for example, one of the reasons the GPL exists.

saurik 13y ago
Right... which makes the argument then pretty obvious: if freeloading is a serious concern, maybe Android should be released in a way that doesn't allow that (closed, GPL, whatever). You are just being needlessly pedantic if you insist the person you are responding to should have said "under a permissive license that leads to the freeloading problem".
- DannyBee 13y ago
  Except his complaint was about openness. So exerting control through GPL would be open, but exerting control outside of GPL is not, even if you exert less control and over less people?
  - saurik 13y ago
    ... the comment went so far as to ask why it was open source at all if there was such concern of a freeloading. The fact that it could remain open source and still avoid freeloading just strengthens that argument and undermines your attempt to defend Google's response to the freeloaders. You also brought up the GPL as the open source way to avoid freeloaders, so your new goal of pretending I'm the one claiming GPL would be "open" (especially when I directly compared it to "closed", not "open") seems to be nothing more than trying to hope I'm too stupid to notice. Again: this is a very simple argument: you seem really angry about freeloaders, and yet you chose the license that allows them to exist: as the person you are responding to said, if you care this much, why did you make everything this open? You could have just made it closed source, or you could have used a more closed (yet user-benefiting!) license such as GPL. To be clear: I empathize with your pain (I made similar licensing mistakes a while ago, and ended up with tons of freeloaders), but I can't empathize with your continued complaints and name-calling as if this is something other people did to you :(. As it stands, you have now built a scenario where the people who play along with you (comply with the CTS, get the Google apps, etc.) are handcuffed (making it not exactly "open" anymore for them anyway) and the people who don't (Amazon) are on your "shit list" (leading to any of new SDK-related terms, new closed critical components, temporary closures that aren't "owned up to" as "closed", and when all else fails: bitter tongue lashings on online forums with negative terms like "freeloader" bandied about)... you are trying to have your cake and eat it too, and that's really disingenuous and entirely low of Google.