4 ms·

That's some impressive revisionist history. The whole reason Steve published that list was because of the backlash Apple received for not supporting Flash.

• jsight 12y ago
  And yet in his own words, the "most important reason" was to prevent other companies from using cross-platform libraries (such as Adobe Air) on the platform. That reason was reversed, and Adobe Air (including what was essentially compiled Flash) became available on iOS. (see daring fireball for more information: http://daringfireball.net/2010/04/iphone_agreement_bans_flash_compiler http://daringfireball.net/2010/04/iphone_agreement_bans_flas...)
  • revscat 12y ago
    It was never reversed, and you're missing the point. Flash as a runtime environment -- with its own stack, VM, APIs, and process ID -- was never allowed on iOS, and only barely was available on other mobile devices. What you linked to was Air, which allowed you to write applications in ActionScript and then generate Objective-C. This is worlds away from a reversal. You were still using Cocoa to interact with the device, not Flash.
    • jsight 12y ago
      It was reversed: http://playcontrol.net/ewing/jibberjabber/apple-ios-license-term-chan.html http://playcontrol.net/ewing/jibberjabber/apple-ios-license-... Also, Adobe Air does not compile to Objective C, though it doesn't run in a conventional Flash VM either. See also: http://www.adobe.com/cn/devnet/logged_in/abansod_iphone.html http://www.adobe.com/cn/devnet/logged_in/abansod_iphone.html http://stackoverflow.com/questions/6903202/adobe-air-ios-packager http://stackoverflow.com/questions/6903202/adobe-air-ios-pac...