Slashdot Mirror
A Peace Plan To End the Flash-On-iPhone Fight
GMGruman writes "As the pro- and anti-Flash camps have hardened their positions, the editors at InfoWorld have come up with a four-point peace plan that would allow Flash on the iPhone while addressing Apple's very real concerns over performance, stability, and security. Readers can vote and comment on the peace plan, which InfoWorld hopes will result in serious talks between Apple and Adobe."
Here:
1. Create a Flash video player plug-in.
2. Put the core Flash technologies into the standards bodies.
3. Create an iPhone-certified SWF exporter for Creative Suite.
4. Explore a Flash app certification process.
It's about Profit going down the drain if Flash apps make it to the iPhone!
Ban both of them?
(Apple fans will mod me troll - but fortunately, there are no Flash fans!)
Here I was thinking they were talking about the lack of a camera flash on the iPhone... I guess Adobe Flash is important too. Whatever makes you happy!
Where's the option for "I support Apple not because I agree with their acceptance policies but because I honestly don't want Adobe's crapware anywhere near my phone!"
After all, unlike my desktop where I can easily -remove- Flash or block it with browser plugins, if Flash is on my phone then they better make sure I can remove it!
The Apple/Adobe fight is about money and control. Apple wants to wall people into their garden and Flash is an impedance to that. Apples banking on their customer loyalty (accept that owning an iPhone/iPad == no Flash) and that HTML5 will replace Flash for video.
If this was only about technological/security hurdles it'd be done and done already. Apple and Adobe have the resources to get this working in short order. The issue is money. No amount of standards and compatibility will get past that.
The decision is Apple's and Apple's alone. Apple has all the cards and has no need to cut any deals. InfoWorld's suggestions fail to take that into account.
There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
it's complete bollocks.
Steve HATES Adobe.
You're more likely to get Steve Jobs to prove at the next Apple Keynote that he really can shit rainbows. "One more thing....."
Please read my Canon EOS tech blog at http://www.everyothershot.com
It's all about not allowing unapproved apps to play on the iProduct. Everything else is mostly an excuse to hide the blatant fact. If it was truly about stability and performance, then iTunes among others wouldn't suck so bad.
1) Forget about it, it's their device and they'll do what they want with it, no matter if you like it or not.
2) Learn another language. WTH is wrong with developers these days? It's not that hard to learn another language! Makes me ponder if most the flash developers are actually programmers or just script kiddies.
3) Web authors: start using HTML5 video standards and quit the stupid flash video player already!!!
Finally: I actually hopes flash dies, I hate the tech on my browsers and hate feeling forced to install it on every computer I have. Flash should die and Adobe should turn all their Flash authoring tools into HTML5 authoring tools instead. Heck, that would get them into the iphone too!!!
This has to be more than just allowing flash movies to play. Adobe would have to allow people to write applications that supports all that is flash. This would clearly get rid of the major worry about Flash, that it is controlled by a single firm that could wipe our it's competitors simply by no longer supporting Flash on their products. Of couse, as Adobe is finding out, it works both ways. Apple is doing it's best to destroy Flash by not supporting it on the mobile products.
Why will Adobe not allow flash players? Well, because then we might get functionality that would be a detriment to major players like google. Users might have in browser control of browser cookies. Users might get the control the do with images, like automatically blocking any flash object below a certain size. Or, heaven forbid, user might get an off switch.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
How do so many people seem to miss the rather glaring issue that Apple has no desire to be a slave to a third party development tool. They've stated as much and it is a very real and serious concern. They offer features to their customers but, if a third party provides developer tools (such as Adobe with Flash) and that third party decides to take their time offering support for those new features or to outright not offer it at all then those features do not make it to the customer. That is a serious concern. In an environment where manufacturers need to provide every advantage possible to stand out from the other offerings on the market, Apple would be hamstringing themselves if they allowed Adobe, rather than themselves, to dictate what features do and do not make it to their customers. Anyone who thinks, even for a second, that this is a trivial part of the equation is not thinking clearly about things.
I'm surprised that InfoWorld completely overlooked this very real and very significant concern. Ah, who'm I kidding?... I'm not surprised at all... sigh...
Apple's new terms forbid applications written in any language that is not called C, C++ or Objective-C. For example, I work on the Free Pascal Compiler and added iPhone support a couple of years ago (it compiles straight to ARM assembler, no intermediate code or frameworks are involved). Most people that use it write their GUI in Objective-C and reuse Delphi or other existing Pascal code for their backend, just like other people would reuse C or C++ code.
But simply because FPC stands for Free Pascal Compiler rather than for Fast Progressive C, this way of working is no longer allowed. That just does not make any sense to me. Why on earth would the name of the programming language matter in any way? I could understand it if they would limit you to using their tool chain (although I'd still disagree with it), but limiting to a particular set of programming languages?
The fact that I can't even discuss this on the iPhone developer forums without first signing the new developer agreement (and thereby make it illegal for me to continue working on that project) only adds insult to the injury.
Donate free food here
Bye. Can I have your gold?
The counterpart to Flash development in the iPhone world is AJAX and HTML5. That's free and you don't need to use the app store. It's called a Rich Internet Application (RIA) or a "web app". The so-called Flash replacement is a Javascript library that makes it easier to write web apps that look like native apps. That will actually help developers who don't want to pay fee or go through the app store. You pay $99 in order to develop native apps for the iPhone - that's different.
Very often, people confuse simple with simplistic. The nuance is lost on most. - Clement Mok
It claims to support SWF1 and a lot of SWF2. Right now I believe we're on SWF9, so there's a long way to go, but it does show that the approach works.
Say Apple releases new API's you want to use in your app. Here's what you do as an Xcode coder:
1) Download the new Xcode with new API's
2) Modify your code to use new API's
3) Recompile
4) Submit to store
Here's what you do if you want to use new capabilities from your Flash app:
1) Wait for Adobe to download new XCode
2) Wait for Adobe to use new hooks in code and expose them to you in new functions.
3) Buy new version of Flash development.
4) Modify your code
5) Export as iPhone app
6) Submit to store
I would rather have to code in Objective-C than wait for and have to buy a new version of Adobe Flash, just to get the capabilities made available by Apple's Xcode.
No it's not. I have the full X-Code package for developing on desktop OSX and iPhone, I downloaded it from the developer's area of Apple's website after registering for free. You only pay if you wish to release software via the App Store for the iPhone/iPad. $99 seems very reasonable to me as a fee for use of the libraries and access to the App store. Many development environments (e.g. Flash) require you to pay up-front whether you release or not.
Surprisingly, you are required to run OSX to run Apple's development environment, just like you are required to run Windows to run Microsoft's development environments. Code can be written for OSX using freely available tools and libraries on the OS of your choice, which will run from the command line or graphically via one of the cross-platform UI libraries. If you want to link against Apple's libraries you will need to use their OS, which I think is true of the Windows APIs too.
I've programmed in a lot of languages. I just learned Flash a few weeks ago because I needed to port an iPhone game to Flash. From a developer's perspective, programming in Flash is like programming with half a language that only has half a run-time library. That wouldn't be so bad if it was fun to program in like some of the more modern scripting languages, but it's not.
Regarding performance, I found that the only way to make Flash code perform well is to write spaghetti code. I had a collision detection routine running really slowly, and when I hacked together a profiler for it (which is not easy because the language has no high-precision timers), I discovered that the function call overhead in Flash is obscenely high. I had to get rid of all getter methods (i.e. make all my read-only member variables public), replace convenience functions like Math.abs() and Math.max() with if-then-else statements, and take my hit test function and copy+paste its contents everywhere I wanted to call it. (I didn't see any macro or inline features, and as much as I hate to copy+paste, the hit really was that bad.)
IMO, if Adobe can't fix the language, they should put a bullet in it. If they won't do either (and they've had years), then I have no problem with other companies attempting to put a bullet in it.
In one thread, I have this going on:
while (Flash.Sucks)
{
Developer.Bitch();
Developer.Moan();
Developer.Complain();
}
While in another thread, I have:
while (Apple.IsBastards)
{
Developer.Bitch();
Developer.Moan();
Developer.Complain();
}
These threads are deadlocked in a race condition, and meanwhile, most Users have absolutely no idea what's going on. Surprisingly few of them even seem to care.
You see? You see? Your stupid minds! Stupid! Stupid!
Because it is the geek version of an 'inconvenient truth". Folks on here love to bash the iPad/iPhone/iPod Touch, comparing it's 'closed' system to a general PC, which is wide open. The argument makes no sense when it is taken for what it is: An appliance.
Apple and Flash Haters in general have very real arguments against the use of flash (for the record, as to performance, if Flash improved in that arena, I wouldn't see an issue from that side of the argument. I could simply make the choice to use or not to use). It is proprietary, it encompasses an framework within itself, and it is out of Apple's control. If Apple were to allow Flash 'apps' on the iPhone, and Flash introduced a security vulnerability across such a large scope of applications (and you know there would eventually be thousands of such apps), Apple would be totally at the mercy of Adobe, who has a terrible track record when it comes to security. In such an instance, it would be Apple who suffered the scorn, not Adobe. Why would any sane person want to put themselves into that situation, when they obviously do not need to? The lack of Flash has arguably not hurt iPhone sales in any significant way.
I also found this statement from TFA a bit ridiculous: "At InfoWorld.com, we believe such lockouts of technology, however well rationalized, could eventually lead to an Internet future of multiple, incompatible platforms that demand multiple proprietary technologies."
The simple fact is, that if a technology is good, and absolutely needed, it will be placed where demanded, or the vendor refusing to will simply shrivel and die. The market ultimately makes this decision for a vendor. Standards group typically end up incorporating technologies when evolving needs require them, although they may take their time, they do eventually get there. These standards don't happen in a vacuum. Prior to HTML5 and no viable alternative to PROPRIETARY Flash, there simply wasn't much of a choice. The market demanded the features that Flash delivered. Even though it is a proprietary technology (like the one the above quote is slamming), it became hugely popular. This in itself I believe was it's biggest downfall. It had no competition within the market, and Adobe became lax with it. They had the 90+ percentile numbers of multitudes of Windows users who were lapping it with nary a choice to the contrary. 64 bit OS's have been around for years, yet we are only now seeing betas of a 64 bit plugin? Smart phones have been around for years, yet we still have no production version of the client. The geek herds should be all up in arms that Flash is so 'last century', yet they are clamoring to get it installed (well at least some are) onto their Droid's, only to complain that it crashes, kills battery life, and generally sucks. Why so surprised?
I'm actually rather shocked that Flash's downfall is so tantalizing close considering it was an almost impossible 'ball' to fumble given the unbelievable good fortune Adobe has had and squandered.
The InfoWorld article misses the point. It is for me the consumer to decide, and I believe the Apple crowd has overwhelmingly already done so, and new the new directions like HTML5's capabilities are a reflection of that (note I'm not saying Apple is responsible for HTML5 or anything of the sort, but their refusal to 'sign on' to Flash due to it's very obvious shortcomings are being answered by new standards to address those concerns).