21–30 of 41 posts
I don't get it. As long as an ARM binary or a 'Super-Secret A4 Architecture' binary is produced, who cares? I can write Objective C code in TextMate and then use xcodebuild from the command line to build a fully functional iPhone or iPad app.
Good, because it's wrong.
but will add tremendous fuel to the fire that perhaps the A4 is NOT an ARM architecture.
No it won't
In fact, it’s highly possible that the A4 is a dual core Power Architecture
No it's not.
If you read other articles from that site claiming that the A4 is PowerPC, it becomes clear that the author came up with the PowerPC theory months ago (before the iPad was released - see http://markstechchat.blogspot.com/2010/02/ipad-saga-week-3-a... for example) and is now grasping at any straw to avoid being wrong.
If all they want is for you to use their compiler/linker, etc. then there should be no reason you can't use a tool that compiles actionscript, javascript, lua, etc down to C code which you then compile with Apple's compiler.
Face it, there are no credible explanations for the new TOS other than simply blocking a competitor (ie, Adobe) from having access to your platform.
Frankly, I'm more than a little surprised to see such a pro-free market crowd as HN so supportive of the new iPhone TOS.
> This incredible foresight will allow Apple to stay agile and maneuver in the face of what will be unrelenting competition I mean, there's plenty of arguments on both sides of it — yay Apple can make changes on a whim, boo my custom-baked solution makes me so productive — but calling it "incredible foresight" is a little overzealous. From Apple's perspective, they want an additional element of control, and to call i…
Sound like bullshit. Apple didn't mandate the use of XCode, they mandated the use of C, C++, or Objective C. They also said you can't use a layer that generates C, C++, or Objective C. If all they want is for you to use their compiler/linker, etc. then there should be no reason you can't use a tool that compiles actionscript, javascript, lua, etc down to C code which you then compile with Apple's compiler. Face it, t…
Sound like bullshit. Apple didn't mandate the use of XCode, they mandated the use of C, C++, or Objective C. They also said you can't use a layer that generates C, C++, or Objective C. If all they want is for you to use their compiler/linker, etc. then there should be no reason you can't use a tool that compiles actionscript, javascript, lua, etc down to C code which you then compile with Apple's compiler. Face it, t…
The free markets argument in favor of the new TOS: it's a free market, and Apple should be able to ship whatever product they want.
I don't get it. As long as an ARM binary or a 'Super-Secret A4 Architecture' binary is produced, who cares? I can write Objective C code in TextMate and then use xcodebuild from the command line to build a fully functional iPhone or iPad app.
Just think about the transition from PPC to INtel. For Xcode users - this was pretty much cake. The had to add some code in some cases, but it was a fairly easy task. If, on the other hand, some other compiler run by someone else, hostile to apple, was the preferred platform for most apple developers, apple would have had a hell of a time pulling off a move like that.