Live data from Hacker News

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

daringfireball.net

231–240 of 495 posts

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

#231
post #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…

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. I think the answer is definitely yes. Apple's software engineering is not that great. There is always some hole in Safari that allows root access to the entire device. They can't get atomic syscalls working in OS X. Does anyone really think they can recruit and affor…

> They can't get atomic syscalls working in OS X.

Have you filed a bug?

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

#232
post #87
post #52

Problems with it aside, and I certainly don't like it anymore then anyone else here (I was still hoping to get a lisp working for iPhone development), I think it would be wrong to attribute the decision to malice. Apple's doing this for the exact same reason they do EVERYTHING else controversial that they do on iPhone OS: because the primary (only?) thing they care about is the end user experience being as good as po…

No, they're clearly doing this to lock people down and prevent strong innovation on their platform. They want tons of toy apps, but nothing threatening. They don't want people abstracting over their platform. They are deliberately restricting developer freedom. If they wanted to avoid crap apps, they would just reject crap apps. They don't care about that. They want to prevent developers from innovating on top of the…

What language and tools do you think Apple uses for the apps they provide and/or sell on the iPhone/iPad?

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

#233
post #137

Earlier quoted context omitted.

If the cross-platform experience is subpar, Apple should just let these apps fail in the market.

"If the cross-platform experience is subpar, Apple should just let these apps fail in the market" Perhaps, like Nintendo, they learned the lessons from the collapse of the home video game market in 1983. When Nintendo was contemplating developing the NES, they took a deep look at what had caused the collapse. What they concluded was that the main cause of death was the market being flooded with too many crappy games.…

There are so many flaws in this reasoning, I don't know where to start.

#1 - Two of the worst carts preceding the '83 crash were E.T. and Pacman, both developed and produced by Atari itself, not these mysteriously inferior 3rd parties you're alluding to. And how many games has Apple, who logically has the most know-how on the platform, produced? None.

#2 - You're making an oranges to apples comparison anyway. The video game market was not crashed by the availability of cross-compilers or tools that lowered the bar of entry. Similarly, Nintendo did not solve the problem by restricting what tools developers could use. They solved it with a strict editorial process.

#3 - Video game production in 1983 required producing and marketing physical goods. It relied on predictable "hits" just like AAA game development to recoup the considerable outlay required to get these games in front of consumers in the first place. iPhones games are virtual and the marketing for many of them non-existent (simply because I can't spend $0.25 CPC on Google trying to sell my $0.99 app). Additionally, there's a long tail of developers creating a more robust landscape of content. There can be tons of failures and still leave plenty of room for successes. Just look at how many games on the iPod have made it big. Many of them came from virtual "nobodies".

#4 - In 1983, there was no manifestation of "wisdom of the crowds" to guide any consumer purchases. Word of mouth was about it. Today, at Apple's scale, one can find dozens of opinions about the quality of a game that only 0.01% of total users may actually purchase.

Many of these problems continue to persist in the locked down AAA console world that you seem to be so fond of. You know, I can accidentally buy 50 terrible iPod games and still spend less money than I would have spent accidentally buying 1 terrible PS3 game.

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

#234
post #144

Earlier quoted context omitted.

Really? Bullshit. You honestly believe that stuff made in Obj-C can only be a toy whereas something written in ActionScript will bring the "strong innovation"? Yes, they're certainly restricting developer freedom (which, again, I don't like any more then anyone else), for the same reason they have been in the past: because they don't want their users to have a shitty experience. I mean, how the hell do you define a "…

Tumult's point is not about writing a single script-based solution but rather about developing an enabling technology for a whole raft of solutions. A platform-on-platform.

Like what? You can't use Objective-C to do something like that?

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

#235
post #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.)

It's almost like refusing to accept patches that are written in anything but vanilla C. It's almost like they are claiming if you can't at least code in C you probably aren't smart enough to submit patches anyway.

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

#237
post #32

Earlier quoted context omitted.

the wording says "Applications must be ORIGINALLY written in Objective-C, C, C++, or JavaScript"

It seems absurd and unenforcable; I mean, applications are originally written in my head.

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

#238
post #205

Earlier quoted context omitted.

We're well past that anyways. 185,000 apps? What percentage of those are complete and utter crap?

A lot less than if Apple had opened the floodgates.

Conversely, how many apps have been made worse by archaic restrictions by Apple?

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

#240

I want to code in Objective-C, and I don't think Android allows that, so I'm stuck programming for iPhone/iPad. I wish Google will support Objectice-C calls against their APIs.

You could write your Android app in Objective-C and then run a program that translates it to Java. Google doesn't prohibit you from doing that.
Post reply on HN