Re: No head for business...
> There is a general misconception that Apple are blocking Adobe's entry into the iPhone market. They are not. They are blocking individuals from using Adobe's software to develop apps for Apple's platform.
I think the main point is being lost here and focus is being place on Adobe because it affects them. However Apple, in their traditionally "lets be vauge to cover case where we want to change our minds, pretend thats what we had in mind from the start or just cover inconsistent application" way, appear to be implying that developers can't use generation tools, platform dependent abstractions.
I rarely develop an application with 100% hand written code, if I do then you can bet it is a trivial application. I, and many people/shops out there would write a DSL (domain specific language), from which an interpreter executes those at runtime or generate java/c/obj-c as applicable. Apple have already had place T&Cs to prevent you from having an interpreter, which while it is pretty poor from my point of view I'll concede the point. However this new change to the T&Cs seem to suggest I can no longer use my generator stragegy, i.e. this seems to prevent me from writing some of my logic in a language I created (or something like flash) and then translating that into objective-c or c++. Obviously iun teh case of flash apps, these would require a flash runtime, but Adobe would have to write this in c/c++/obj-c and the deveopers app would have to link against that.
Apple appear to be implying that you can't use libraries that abstract away the underlying OS, allowing the developer to code against another library, that library then calls the relevant runtime library. Software developers have been using this approach pretty much for the whole history of programming.
The point is why should apple dictate what I language write my application in, as long as it does not call teh so called "private" API and does not interpret code at runtime (guess that rules out algebraic calculators?) what concern is it of theirs, it's an implemenation issue. What next, I have to use xcode to type the actual code instead of emacs, hell I even write some of the code under linux.
The only reason I can think of is that would make it harder to support multiple platforms, as we won't be able to write apps in something neutral and then compile that into something runnable on iphone, andrond, mac/win/linux desktop, web app. Maybe developers would have to prioritize platforms and the iPhone is (currently) the leader
> Apple are also blocking Adobe's proprietary runtime from their OS--again, nothing illegal about that.
What is different to that and using any other library from a third party. As long as that runtime is not calling an <illegal> api method or interpreting any code, I'd expect it to simply translate the intent into the relevant iphone method, that coupled with a tool from above to turn your flash to objective-c or an compiled object file/library so that there is nothing interpreted.