Objective C code lockout
|
| Author | Content |
|---|---|
| lsatenstein Sep 14, 2010 11:15 AM EDT |
In a small minded approach, looking at today's profits only, by making O-C locked out, this action locks out many developers who can't pays Apples compiler fees. When developers are locked out, and Gartner tells us, that Android will take over the market by 2014, it seems that developers will switch their allegiance to develop for the Android. I think that I am super happy I did not buy into the Apple product line. I have no commitment to developing for a me-only company. |
| gus3 Sep 14, 2010 1:32 PM EDT |
If GCC is licensed under the GPLv2/3, then two things are true: 1. Apple must supply whatever patches they have applied to the GCC source code base, as well as (a link to?) the source code base to which they apply those patches, for whatever Apple-published version a user may obtain, and Apple must supply these on demand of anyone to whom Apple has supplied the binaries built from these. 2. Once someone receives these (source code plus patches), Apple cannot restrict what the recipient does with them, as long as the recipient complies with the terms of the GPLv2/3. An NDA would violate both versions 2 and 3 of the GPL. So what's to stop someone from demanding, and then publishing the patches where the GCC project can find them? |
Posting in this forum is limited to members of the group: [ForumMods, SITEADMINS, MEMBERS.]
Becoming a member of LXer is easy and free. Join Us!