3 ms·

this interpretation of the new rule is insane OK, I'll bite. What's the correct interpretation, according to you?

tptacek 17y ago
Presumably it's "as long as you're using the Cocoa Touch stack as your primary development environment, we don't care what other tools you use; however, if you want to use Flash, develop for a different phone."
- stcredzero 17y ago
  Insane? No. Worrisome in its arbitrary restrictiveness? IMHO very much!
  - tptacek 17y ago
    Since my memory span goes more than a year or two back, I vividly recall Apple shipping a product that had native app development available only to Apple. I simply don't believe that Apple owes everyone Flash. Maybe this will get different when Apple owns 70% of the smart phone market. Right now, people are upset about not being able to use their preferred tools on the coolest phone. But they have no inherent right to develop on the coolest phone.
    - andygeers 17y ago
      Some of us have already invested over a grand buying Macbooks and Unity licenses and test iPod Touches specifically so that we can develop games for the iPhone, though... Would have been nice to have known in advance that this would be ruled out!
      - tptacek 17y ago
        Conceded completely: that sucks.
        stcredzero 17y ago
        This is a step above just saying, "It's our ball, you can't play!" This is waiting until someone goes and buys a bat and only then telling them they can't play.
        tptacek 17y ago
        And that's where you lose me. It sucks to be out $2000 and having the terms changed on you. I hope they get refunds. But keeping Adobe out of the iPhone dev tools market doesn't suck at all. It's a totally rational decision and while it is not the decision I would make, I will in the end probably benefit from it.
        stcredzero 17y ago
        I agree with you: the fact that this is happening to Adobe mitigates it somewhat for me, but that doesn't make the maneuver in the abstract any less severe. This is getting to the level of Microsoft telling everyone that the MFC is the way to go, but later on people discover that Microsoft is using something else internally for GUIs.
- wvenable 17y ago
  Yes but this excludes tools, such as MonoTouch, which actually do use the Cocoa Touch stack but allow you to code in C# rather than Objective-C.
  - tptacek 17y ago
    Are they wrong about MonoTouch? Probably yes. They're not going to do everything right.

Presumably it's "as long as you're using the Cocoa Touch stack as your primary development environment, we don't care what other tools you use; however, if you want to use Flash, develop for a different phone."

stcredzero 17y ago
Insane? No. Worrisome in its arbitrary restrictiveness? IMHO very much!
- tptacek 17y ago
  Since my memory span goes more than a year or two back, I vividly recall Apple shipping a product that had native app development available only to Apple. I simply don't believe that Apple owes everyone Flash. Maybe this will get different when Apple owns 70% of the smart phone market. Right now, people are upset about not being able to use their preferred tools on the coolest phone. But they have no inherent right to develop on the coolest phone.
  - andygeers 17y ago
    Some of us have already invested over a grand buying Macbooks and Unity licenses and test iPod Touches specifically so that we can develop games for the iPhone, though... Would have been nice to have known in advance that this would be ruled out!
    - tptacek 17y ago
      Conceded completely: that sucks.
      - stcredzero 17y ago
        This is a step above just saying, "It's our ball, you can't play!" This is waiting until someone goes and buys a bat and only then telling them they can't play.
        tptacek 17y ago
        And that's where you lose me. It sucks to be out $2000 and having the terms changed on you. I hope they get refunds. But keeping Adobe out of the iPhone dev tools market doesn't suck at all. It's a totally rational decision and while it is not the decision I would make, I will in the end probably benefit from it.
        stcredzero 17y ago
        I agree with you: the fact that this is happening to Adobe mitigates it somewhat for me, but that doesn't make the maneuver in the abstract any less severe. This is getting to the level of Microsoft telling everyone that the MFC is the way to go, but later on people discover that Microsoft is using something else internally for GUIs.
wvenable 17y ago
Yes but this excludes tools, such as MonoTouch, which actually do use the Cocoa Touch stack but allow you to code in C# rather than Objective-C.
- tptacek 17y ago
  Are they wrong about MonoTouch? Probably yes. They're not going to do everything right.