How many people upset over Apple's rules are actually iPhone developers?
chriseidhof: I think this is great news for "real" iPhone developers.The good thing about being an ObjC iPhone-developer is that there aren't that many iPhone developers.  So if you're producing decent stuff (or better, of course), you'll be in high demand.  I'm not sure for how long you'll be in high demand, but I think this is a great move from Apple for ObjC-developers. It makes them in even higher demand. Anybody can program in Flash or Java, but learning ObjC is a bit different and perceived as more difficult, due to things like no automatic garbage collection and (sometimes) low-level C APIs.  All those developers that have invested their time in learning these things are now rewarded by Apple.I used to be an iPhone developer, and although it's really good for making money, I was personally frustrated by Obj-C.  It's not that I can't program in it: I've been making good money from it for over a year.  It's just that I also program in Haskell, and that is just such a better fit for me.  I guess it's really a personal thing.  I've decided to quit before I grew really frustrated, and start doing things I love.  I'm not sure if it's a wise thing, but it works for me.I was hoping that someday in the future we could use Haskell on the iPhone, either via the arm-ghc, jhc (which can compile to ansi C) or DDC (a Haskell-variant).  So it's too bad that this isn't going to work anymore.To answer the question: I stil consider myself an iPhone developer, and I am a bit upset.