Live data from Hacker News

New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

daringfireball.net

11–20 of 495 posts

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#11
post #7

Would Adobe have a valid antitrust case with this?

Nope. Apple doesn't have a monopoly in the phone market.

How is "market" defined, legally? They certainly have a monopoly over the "iPhone" or "iPhone App Store apps" markets. Of course, that reasoning could get absurd pretty quickly, so I'm sure it must be defined at a pretty generic, high level.

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#12
Say hello to the new boss, same as the old boss. The corporate pissing matches have started in earnest...

When Alan Kay said Apple would take over the world with an iPad, I don't think he realized that eToys or anything like eToys would never be allowed to run on the device and that a majority of the apps will probably have commercial spots embedded within them. Actually it reminds me of "educational" tv all over again...

I'm starting to see the point of people who complain about the consume vs. create nature of the iPad...

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#13

I find it same time amusing and hard to believe that this kind of requirement (writing apps only in C++ & Obj-C) is legally possible.

I'm pretty sure that it's legally possible. It's a contract and I don't think that this restriction would be struck down by any court as being not valid.

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#14
I don't like this at all. Maybe they only meant to hit Flash, and maybe not, but as written this is in direct opposition to one of the most important principles of software development. Apple themselves must have benefited countless times from writing software in layers. But no layer above their layers is permitted?

I wonder if the open source world can successfully fight back, by making compilers that generate code the app store police can't tell from hand written.

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#15
post #8

I don't really have a politically correct way to say this: What a horseshit maneuver by Apple.

I have been a very loyal mac user for years and love it, but I'm seriously considering going back to Linux. I am not a free software "zealot" and don't mind some closed-ness, but this is getting absolutely insane.

Enforcing which LANGUAGES can be used on a platform?!? Insane!

Edit: I've been looking at these guys:

http://www.system76.com/

(I don't work with or have any vested interest in them, but they look cool.)

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#16
post #13

I find it same time amusing and hard to believe that this kind of requirement (writing apps only in C++ & Obj-C) is legally possible.

I'm pretty sure that it's legally possible. It's a contract and I don't think that this restriction would be struck down by any court as being not valid.

Contracts of adhesion often are often found Unconscientious and not enforceable.

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#18
> Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine

Controlling programmers like this seems positively insane, doesn't it? Does this mean that games can't do scripting in something like Lua either, under the letter of Apple's law?

Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others

#20

Is there a legitimate reason for this, or is Apple just thumbing their noses at Adobe (and everyone else)? Is Apple primarily annoyed that Adobe's app and MonoTouch aren't doing it the "Apple" way? Or do they not like that those frameworks present non-standard UI's (I haven't used MonoTouch, so I don't even know if that's the case here)?

MonoTouch uses Cocoa bindings, so the interface is using native components.
Post reply on HN