News for hackers. Stuff that matters.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by spolsky on Thursday April 08, 2010 @04:58PM (#1250911)
the wording says "Applications must be ORIGINALLY written in Objective-C, C, C++, or JavaScript"
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by aheilbut on Thursday April 08, 2010 @05:03PM (#1250936)
It seems absurd and unenforcable; I mean, applications are originally written in my head.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by funxed on Thursday April 08, 2010 @05:51PM (#1251124)
Since Apple completely controls the App Store and reserves the right to refuse any app for any reason (and have shown time and again they are willing to exercise that right), how could this possibly be unenforceable? It is their way or the highway. What is or isn't enforceable is entirely up to them.

Note: I am in no way saying that Apple's stance on this situation is a good one or not, in face, absurd. The iPhone 3G is the last Apple product I will ever buy because of this and other iPod/iPad related anti-developer bullcrap.

Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by aheilbut on Thursday April 08, 2010 @06:15PM (#1251189)
Unless they start auditing source code and everyone's entire development process, there are lots of ways in which such a rule could be violated that would be completely undetectable (and some cases that would be easily detectable too).
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by anigbrowl on Thursday April 08, 2010 @07:06PM (#1251336)
Quite, but would you admit publicly to having done so?
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by carson on Thursday April 08, 2010 @07:13PM (#1251355)
I think you have it there. Developers probably need to be ready to submit their source code along with their binary. That is my guess on what will happen when one sees the "denied because it isn't hand written."

What this will absolutely stop is Adobe calling out developers who have added apps to the app store compiled with CS5. Those apps created that way will also be unable to move upwards to the new OS version. I would imagine it will also completely stop Adobe and others from any development on any OS 4 bridge because they would have to agree to the license to test against the actual SDK and they can't do that without legal problems.

Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by die_sekte on Thursday April 08, 2010 @05:32PM (#1251051)
Next up: Only non-sentient developers allowed.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by MutantSushi on Thursday April 08, 2010 @07:39PM (#1251422)
Quite. How does one extend this to real-world languages? "You must originally compose message board posts in English" So, nazi mind-readers to detect those secret English-as-2nd-Language speakers who are secretly, nefariously still thinking first in their native language before rephrasing it in English?
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by jrockway on Thursday April 08, 2010 @05:39PM (#1251085)
I've just invented a new language: C2010. It looks exactly like ActionScript, for some reason...

(Hint: Apple's version of C is unlike any standard version of C, like C99. So technically, you can't use Apple's tools. Or, you can call anything you want C, just like they do.)

Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by halostatue on Thursday April 08, 2010 @08:00PM (#1251460)
This is incorrect. Apple's C is C99; they have also introduced a new optional syntax for blocks that they have submitted for standardization.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by jrockway on Thursday April 08, 2010 @09:55PM (#1251619)
Right, and $foo is just C but with $bar.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by sparky on Thursday April 08, 2010 @10:04PM (#1251635)
To be fair, all widely-used C compilers I am aware of have extensions to the C90 and C99 standards, which they accept as conformant code by default.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by jrockway on Thursday April 08, 2010 @11:13PM (#1251756)
Sure, and that's fine. What Apple is doing is saying, "you must use C" without actually defining what "C" is.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by wglb on Tuesday April 13, 2010 @08:05PM (#1263750)
There was a hacker news discussion a while back by one of the principals of Coverity in which they asserted, with no small experience, that there is no such thing as a C language. This is due to the wide number of variations in what compilers accept and that users of C compilers expect.

Sure there is an ideal, but practically, there is not consistent definition of the C language.

Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by sparky on Wednesday April 14, 2010 @01:31AM (#1264223)
The article discussed was this one in CACM (link is to discussion on Lambda the Ultimate) http://lambda-the-ultimate.org/node/3824 . I remember seeing it on HN too, but couldn't find the page immediately.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by halostatue on Friday April 09, 2010 @10:38AM (#1252781)
Wrong.

Apple's C is C99 (as implemented by both gcc and clang). If you wish to take advantage of something like Grand Central Dispatch, they recommend that you do so with their completely optional syntax for blocks (which, aside from being closures AFAIK, are essentially anonymous functions in situ instead of defining a function externally).

You can still use GCD without the new block syntax by using function pointers, leaving you with bog standard C99.

Frankly, gcc implements a lot more non-standard stuff on its own than Apple's blocks have introduced.