David cgc wrote:
And that's splendtacular, but you aren't going into what happens when middleware goes wrong. What happens when popular apps are developed with MonoTouch? It's all gravy now, but what happens in five or six years, when OS X develops in some way MonoTouch hadn't anticipated, or they don't update for whatever reason? Then all those killer apps become a millstone around Apple's neck, and they have to keep bending over backwards to support legacy technology.
Yes, and? How is this different from everyone else? What makes Apple so unable to deal with legacy support on their mobile platform when a) they do it fine on OSX and b) everyone else has to deal with it too? Of course Apple had absolutely no problem with middleware on the iPhone before... they've even gone so far as to demo apps created with it live on stage by Jobs himself. Obviously these apps were good for something! What a coincidence, then, that middleware was banned just
as Adobe was about to release CS5 and just
as Android was starting to put pressure on Apple. Apple owes part of its success in the iPhone to middleware, but now that it's more useful to them as a way to attack their competitors they've turned it into a weapon.
Meanwhile, the developers are stuck in the crossfire and the consumers get hurt without even realizing it. The only one who wins is Apple and the entire
mobile industry will suffer for it.
I do certainly agree that there is psychology at play... Apple did, as you point out, get burned by 3rd parties in the past. And now they've swung around the other way, become a total control freak about it and in doing so are now exerting control on other
platforms too. It's like seeing a kid get beat up and turning into a bully as a result. Yes, what happened in the past sucks, but it doesn't excuse anti-competitive behavior.
What it essentially comes down to is that this is an argument against cross platform development as a whole... and that's the road Microsoft went down in the 90's. And we all know where that road leads.
Yup, there's some great things you can do with HTML5. That's not the point. The point is that Apple should not be dictating the direction that the entire
web moves in. If this wasn't Apple but instead Google refusing to, say, return sites that use Flash as search results I'd be making the exact same argument. Apple can say that they're just supporting open standards, but if they're doing it by blackmail it isn't exactly a choice now, is it?