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.
New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
211–220 of 495 posts
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#212Getting away from the frenzied rhetoric, my opinion is that what Apple really wants to prevent is people releasing multi-platform compilers. So taking Flash as just one example, if I can build one app and the compiler can make me an iPhone executable, an Android executable, and so forth, Apple don't want that. In my experience so far with such "cross platform compatibility layers," they always produce results that wa…
This is seriously putting me off. I was not thinking of a third party approach, but it limits me when I want to use my OWN scripting language when developing apps.
Does this stretch to build scripts??
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#213Okay, there is ECL (Embeddable Common Lisp) which has been hacked up to work on the iPhone. It compiles to C. I can't use it? I hope there are other companies that will release usable tablet hardware.
I'm no Clojure fan, but if you want to write Lisp-like for a phone, why not Android? Your Clojure app can run on everything from the G1 to the Nexus One to the Archos 5" and 7" tablets, not to mention the wide variety of no-name Chinese tablets that run Android. I've heard you can even get a SLIME/Swank REPL from the emulator or actual hardware. Seems like this beats the iPhone any day; better development cycle, and…
If I won't write for Apple, why should I write for Google (aka 'the NSA frontend') and their OS?
The only useful alternative will be a 'free' Linux derivative that does not restrict me in my developer choices and does not want to collect all kinds of data.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#214Earlier quoted context omitted.
Yes, but then the app still wouldn't be "originally written" in Objective-C.
And how could this ever be proven?
This is addressed in the original post. As of now, projects that were made other the the approved ones would have obvious file layouts characteristics.
Theoretically, you could make it hard to tell the difference, but in practice its pretty easy to tell machine generated from human written code.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#215Earlier quoted context omitted.
I am not sure that it'll be exceedingly difficult to determine if an app was compiled using another tool, and not written in Objective-C. I'd expect many languages and frameworks are going to have many very signature functions and patterns of code. If Apple decides to enforce this, they won't have a hard time. On top of that, if they miss it, and let a bunch of apps in, then later on determine those apps were crossco…
But of course, this makes for unhappy users too. "I just lost the $5.99 I paid for that app!"
Easy - they can and should just refund the money if they take the app away.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#216Earlier quoted context omitted.
"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.…
Couldn't you have a non-fascist solution to this? Do something like Reddit, Digg, or Hacker News... let people guinea-pig apps and upvote/downvote them and sort in each category.
Because those sites aren't full of bullshit...?
(HN is, IMO, above the rest but it's certainly not immune to mob rule)
Besides, with the money involved in high rankings you'd have to constantly police the system against gaming, which would be, I'm guessing, more work than policing the submissions directly a they do now.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#217Earlier quoted context omitted.
Interpreters were already prohibited.
Interpreters being banned is old news, this is about compiled stuff being rejected because you chose a 'wrong' language.
That's what I said. The comment I replied to is about the potential for educational apps that require interpreters, which were already prohibited.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#218Earlier quoted context omitted.
Sure, 'multiplatform compiling/targeting' is one thing. But banning non-approved languages is silly. Even apple is funding projects like RubyCocoa and bringing Python compatability to the Cocoa API. If somebody wants to write an app using CocoaTouch but finds Ruby, Python, Lua, or Mono to be a better fit for the project or their own capabilities than Obj-C, why stop them from doing so? If the apps still have to inter…
Think OS/4, think opening up multitasking to 3rd party apps, perhaps thats why they are being so anal about how apps should be written, if they are planning to make changes to the low-level libraries to support 3rd party app multitasking then they are going to want to make sure that 3rd party apps are linked against them.
what does language have to do with that? you can include your own C libraries within your project if you want, the language is no different. if people use other language interfaces to Cocoa, like RubyCocoa or MonoTouch, what is the problem, they are still using apple's libraries. the language has nothing to do with any of that.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#219I 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…
Even if it can, that's not the point.
Is this the kind of company you want to build software for? This is bullshit. Do I really even want to play along anymore?
This company makes great products, but they can do completely dickish things.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#220Earlier 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.…
Except most iPhone apps accepted to the store already are utter crap.