DRACONIAN CONTROL

We believe that we need to own and con­trol the pri­mary tech­nolo­gies behind the prod­ucts we make, and par­tic­i­pate only in mar­kets where we can make a sig­nif­i­cant contribution.

Tim Cook, Apple COO

Whenever you feel the need to ask why Apple does shit like fuck-banning Flash or Flash based apps, or when­ever you want to know why Apple doesn’t pro­duce a par­tic­u­lar model of com­puter, reflect upon the above quote from Tim Cook. This couldn’t be more obvi­ous if Apple wrote it in 360 pt. red type on their home page.

Update

  • Umbongo

    The flash plu­gin is a rot­ten pile of junk on Mac, I fully sup­port them block­ing it. But block­ing devel­op­ers from using CS5 to build iPhone apps is a bad move, no doubt Adobe will see Apple in court soon enough.

  • http://www.theangrydrunk.com The Angry Drunk

    And on what grounds could Adobe pos­si­bly sue Apple? Please enlighten me.

  • http://mangochut.net/ man­gochut­ney

    This post fails SO HARD. You lured me here with the word ‘dra­con­ian’, yet you fail to post even one pic­ture of Princess Ardala? WTF?

    Other than that: This level of con­trol is, sim­ply put, what makes an Apple prod­uct an Apple prod­uct. I hope that peo­ple will bitch as hard when Microsoft rolls out Windows Phone 7. My pre­dic­tion is that not only will it be equally sand­boxed, but MS will pro­vide a less com­pre­hen­sive set of devel­op­ment tools and devel­op­ment guidelines.

  • http://www.theangrydrunk.com The Angry Drunk

    Ok ya’ whiner…post updated.

  • http://mangochut.net/ man­gochut­ney

    Much bet­ter! Thanks.

  • http://esthermofet.com esther­mofet

    Let’s see…

    1. Company A makes a prod­uct to enable com­pany B to cre­ate appli­ca­tions and tools on com­pany C’s prod­uct, to be used by con­sumer D.

    2. Companies A & B — who are now in a joint ven­ture — develop, pro­mote, and deliver soft­ware that are impos­si­ble to use on com­pany C’s prod­ucts to con­sumer D. No, really. I mean impos­si­ble. Just try using a Flash app — any app — that requires hov­er­ing on a touch screen. I dare you. (I double-dare you moth­erf… I digress).

    3. Consumer D becomes frus­trated with the appli­ca­tions devel­oped because the inter­faces are bug-laden, atyp­i­cal, impos­si­ble to use, or because bat­tery life that was pre­vi­ously 16 hours now drops to about 17.2 min­utes.

    4. Consumer D then approaches com­pany C to request a fix for the prob­lem, which was pro­moted by A & B and will­ingly imple­mented by con­sumer D.

    5. Angry con­sumer D and com­pa­nies A & B, now join in a slan­der­ous cam­paign against com­pany C.

    6. Company C says, “Get the fuck out.“

    Yeah, sorry, that’s all I got. You’re right — they got nothin’. Looks like Adobe, the pis­sant devel­op­ers, and whin­ing con­sumers can just learn to get over it… or face a countersuit.

  • hav­ochaos

    Well, maybe Adobe has hired Darl Mcbride onto their fine team.

  • Scruff

    Fuck flash. Adobe had five years of piss­ing on Apple users with a
    buggy, slow and bloated player. They ignored Apple because Windows was
    a big­ger tar­get, and treated Mac users like sec­ond class cit­i­zens.

    Now the iPhone is a big tar­get, and Adobe is whin­ing like lit­tle
    bitches that Apple doesn’t want they buggy crap on their phone. Boo
    fuck­ing hoo.

    Adobe has yet to pro­duce a reli­able, fast ver­sion of Flash for ANY
    mobile device… PERIOD. Why should Apple trust Adobe at all? Who’s to
    say that a year down the track Microsoft doesn’t get into bed with
    Adobe, and they let their iPhone ver­sion lan­guish in favour of
    Microsoft Phone Series 7 (or what­ever the fuck it is called today)
    ver­sions?

    Apple is right to ignore Adobe on this one. Apple spent huge dol­lars
    on per­fect­ing their vision for the iPhone, they’re not going to let
    Adobe lower their stan­dards or hold them to ransom.

  • http://facebook.com/profile.php?id=746492945 Mark Thomas Stone

    Nice pic­ture. Where is Buck when we need him?

  • http://facebook.com/profile.php?id=746492945 Mark Thomas Stone

    Nice pic­ture. Where is Buck when we need him?

  • http://facebook.com/profile.php?id=746492945 Mark Thomas Stone

    But even that is dif­fer­ent than ban­ning dev tools that would sup­port mul­ti­ple plat­forms. At the end of the day, even if I devel­oped my Ap in a Flash com­pat­able tool, I still have to con­vert it to make the Apple Approved API calls in “Apple-Speak” before it would even run on Apple equip­ment. Apple’s API struc­ture ensured no “flash-hattery” made it to the iStuff. The new update to the devel­oper agree­ment doesn’t ban flash, it puts undue finan­cial respon­si­bil­ity on the inde­pen­dent devel­oper who wants to develop for mul­ti­ple plat­forms. It is still the developer’s choice if they con­tinue to dev for iStuff, but I think this might not work the way Apple thinks it will.

  • http://facebook.com/profile.php?id=746492945 Mark Thomas Stone

    But even that is dif­fer­ent than ban­ning dev tools that would sup­port mul­ti­ple plat­forms. At the end of the day, even if I devel­oped my Ap in a Flash com­pat­able tool, I still have to con­vert it to make the Apple Approved API calls in “Apple-Speak” before it would even run on Apple equip­ment. Apple’s API struc­ture ensured no “flash-hattery” made it to the iStuff. The new update to the devel­oper agree­ment doesn’t ban flash, it puts undue finan­cial respon­si­bil­ity on the inde­pen­dent devel­oper who wants to develop for mul­ti­ple plat­forms. It is still the developer’s choice if they con­tinue to dev for iStuff, but I think this might not work the way Apple thinks it will.

  • http://facebook.com/profile.php?id=718094082 Darby Lines

    You’re not get­ting Apple’s con­cern here. Apple wants to assure that appli­ca­tions writ­ten for the iPhone OS are capa­ble of fully uti­liz­ing the fea­tures of the OS, not just the sub­set that, for exam­ple, Adobe makes avail­able. Take the mul­ti­task­ing APIs intro­duced in OS 4. It is almost cer­tain that Flash CS5 can­not access them, and it’s equally cer­tain that, were Apple to allow Flash cross-compiled apps, Adobe won’t add those APIs until CS6 is released how­ever many years from now. For a much more in depth analy­sis of the sit­u­a­tion read thishttp://www.devwhy.com/blog/2010/4/12/its-all-about-the-framework.htmlAs to the cost to developers…bullshit. The min­i­mum out­lay to become an iPhone devel­oper from scratch is the cost of a Mac Mini and a devel­oper license. All told, 700 bucks. How much does CS5 cost?

  • http://facebook.com/profile.php?id=718094082 Darby Lines

    You’re not get­ting Apple’s con­cern here. Apple wants to assure that appli­ca­tions writ­ten for the iPhone OS are capa­ble of fully uti­liz­ing the fea­tures of the OS, not just the sub­set that, for exam­ple, Adobe makes avail­able. Take the mul­ti­task­ing APIs intro­duced in OS 4. It is almost cer­tain that Flash CS5 can­not access them, and it’s equally cer­tain that, were Apple to allow Flash cross-compiled apps, Adobe won’t add those APIs until CS6 is released how­ever many years from now. For a much more in depth analy­sis of the sit­u­a­tion read thishttp://www.devwhy.com/blog/2010/4/12/its-all-about-the-framework.htmlAs to the cost to developers…bullshit. The min­i­mum out­lay to become an iPhone devel­oper from scratch is the cost of a Mac Mini and a devel­oper license. All told, 700 bucks. How much does CS5 cost?

  • http://facebook.com/profile.php?id=746492945 Mark Thomas Stone

    Well yeah if you don’t count the labor of dual-developing as cost. There will be guys that have make the choice one way or the other. I will check out the link. Thanks.

  • http://facebook.com/profile.php?id=746492945 Mark Thomas Stone

    Well yeah if you don’t count the labor of dual-developing as cost. There will be guys that have make the choice one way or the other. I will check out the link. Thanks.

  • http://www.bynkii.com/ John C. Welch

    well, it is how Adobe deals with peo­ple not doing what they want. they threat­ened Microsoft with law­suits until Microsoft pulled native PDF gen­er­a­tion from Office 2007. Of course, Apple is far more likely to tell Adobe to go fuck them­selves if Adobe does sue, because paint­ing Apple as a cell-phone, or even smart-phone monop­o­list is kind of not happening.

  • http://www.bynkii.com/ John C. Welch

    well, it is how Adobe deals with peo­ple not doing what they want. they threat­ened Microsoft with law­suits until Microsoft pulled native PDF gen­er­a­tion from Office 2007. Of course, Apple is far more likely to tell Adobe to go fuck them­selves if Adobe does sue, because paint­ing Apple as a cell-phone, or even smart-phone monop­o­list is kind of not happening.