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

5 of 495 comments (clear)

  1. Waste of time by DaveV1.0 · · Score: 4, Interesting

    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.
  2. Re:Not about Perf, Stability or Security by bluesatin · · Score: 4, Interesting

    It's important to note that the loss of profit may not be from the App store, but from the fact that people will have little reason to buy an iPhone if every app is available on every platform; Apple makes the majority of it's profit off hardware not software.

  3. One good idea by fermion · · Score: 4, Interesting
    The article has one good idea, create a flash standard, which I believe would allow others to write browsers with native flash support. This would be the same thing Adobe did when they let others write applications to display PDF.

    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
  4. Re:Apple Plan by uglyduckling · · Score: 4, Interesting

    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.

  5. Flash from a developer's perspective by s_p_oneil · · Score: 4, Interesting

    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.