Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

daringfireball.net

Post reply on HN
Print view View original

91–100 of 495 posts

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

#91

Post by sshumaker »

gojomo wrote: post #42
swilliams wrote: post #2

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)?

Apple might say the rationale is to allow easier inspection of apps for policy compliance. (Even though other languages compiled-to-approved-languages will be the same for automated analysis, it's more likely the code will be inscrutable to human reviewers.)

You don't submit your source code to Apple. Why should this matter?

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

#92

Post by markkoberlein »

Zak wrote: post #75
api wrote: post #15

Earlier quoted context omitted.

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.)

Boycotting the Mac platform (which is pretty much free of any such absurdity) doesn't make a lot of sense to me. That's where Apple is doing things right . You should of course, shun iPhone OS devices if you feel this way. The system76 laptops are probably generic machines from Clevo, Sager or some such with a custom badge. Alienware used to do the same thing.

I wonder if Leo Laporte is going to be right about how he thinks that will Apple eventually stop making macs so that they can focus on more closed or controlled platforms like the iPod, iPhone, and now the iPad. They seem to be pretty good at making money with the closed systems.

Maybe the next iBook will just be a foldable iPad with the same closed OS.

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

#93

Post by radley »

rimantas wrote: post #84

Adobe will not be happy about this, which makes me think: given how events unfolded recently in Adobe-Apple relationship and given that Photoshop is getting crappier and crappier in its OS X incarnation—has Apple some Photoshop/CS analog in the works?

http://www.apple.com/aperture/

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

#94

Post by rimantas »

orangecat wrote: post #69

1. Apple takes iPhone stability and security Very Seriously. 2. ??? 3. Therefore, if you write native iPhone apps, you must use C derivatives that expose raw pointers and direct memory access.

Yeah, as if Flash is known for its stability (especially on the Apple platform) and security…

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

#95

Post by kqr2 »

Zak wrote: post #75
api wrote: post #15

Earlier quoted context omitted.

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.)

Boycotting the Mac platform (which is pretty much free of any such absurdity) doesn't make a lot of sense to me. That's where Apple is doing things right . You should of course, shun iPhone OS devices if you feel this way. The system76 laptops are probably generic machines from Clevo, Sager or some such with a custom badge. Alienware used to do the same thing.

Yes, but it's the content creators that are developing the apps and making the iPad/iPhone a more valuable platform.

Boycotting Apple's content creation tools and consequently not developing for the iPad/iPhone is one way to send a message.

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

#98

Post by bitwize »

ptomato wrote: post #58
telemachos wrote: post #50

Earlier quoted context omitted.

but hey, nobody has to use iAds Yet.

Well, Steve did flat-out say in the Q&A session today that they weren't going to require anyone to use their built-in services for any of that, and Apple doesn't really have a history of changing what they've said they're gonna do.

"Your contract when you buy the iPad is you're going to watch the spots. I guess there's a cetain allowance for people going to the bathroom..."

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

#99

Post by axod »

wvenable wrote: post #85
axod wrote: post #70

Earlier quoted context omitted.

It'll get there... You can already have access to the multi-touch stuff via javascript. idk, I've never thought the appstore was anything but a stop gap personally, and developing for it a crazy risk.

It won't get there before the iPhone is obsolete. You really think that web apps are ever going to get access the microphone or the camera? Also, a stop gap? I think there's an app for that.

>> "You really think that web apps are ever going to get access the microphone or the camera?"

Definitely, if other phones or devices have such capabilities, and a killer webapp comes out that uses them.

If I was Apple I'd just shut the App store down to get rid of all the ungrateful developers. Sorry, but it's their show. They get to decide if you can play, and what the rules are. If you don't like it, don't play with them.

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

#100

Post by jrockway »

axod wrote: post #56
icey wrote: post #8

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

Just make a webapp :/ all the freedom you need.

Seems like Apple thinks the same restriction applies. If you use parenscript or coffeescript (or GWT) to generate your JavaScript, you are technically violating the contract you signed with Apple.

Of course, if you didn't sign that, then you can do whatever you want.

Post reply on HN