Why does everyone act like the iPhone should be as 'open' as an OS on your computer? Did everyone forget that when the iPhone shipped you couldn't write apps at all? You can't write apps in Erlang for your Zune, your PS3, your cable modem, your microwave, your car or your apartments alarm system... no one cares.
Yes, Apple wants (insists, even, if this ToS becomes final) you to use their tools, their stack, etc for making apps on their consumer electronics device - shocking? No. Annoying? Of course. Don't like it? Go somewhere else!
"Did everyone forget that when the iPhone shipped you couldn't write apps at all?"
Yup. And did you forget all the complaints about that too and then the jailbreaking and then the development of apps without any SDK at all? You have to wonder if Apple would have ever created the app store if programmers hadn't done all that.
"Why does everyone act like the iPhone should be as 'open' as an OS on your computer?"
Why shouldn't it be? You act like merely complaining about something should be a crime. If Apple is well within their rights to do what they want with their platform, we're well within our rights to complain about it.
Considering the level of polish on the Cocoa Touch frameworks and the surrounding tools at release I'd say Apple was planning the AppStore long before the mob started RABBLE-RABBLE-ing about it.
Still, I am absolutely not saying you shouldn't be allowed to complain. My point is only that I don't see what there is to complain about. I wouldn't complain about this any more than I would about not being able to write apps for my current crappy cellphone. It isn't even that bad though, of course, because you can write apps for the iPhone, just not in arbitrary ways that Apple doesn't approve of.
Anyway, it's ok that we don't agree -- it seems, at this time, that Apple and I are on the same page... We'll see if things change or not. I am obviously all for Apple being more open in general (having to use a Windows VM to sync my iPod is a huge pain in my ass, for example), I'm just not losing any sleep over it.
> My point is only that I don't see what there is to complain about. I wouldn't complain about this any more than I would about not being able to write apps for my current crappy cellphone.
Really? When I had a crappy cellphone, I complained that the WAP browser was constrained to my provider's walled garden. I managed to crack it enough get out and even write my own WAP applications. So not only did I complain, I did something about it.
I also complain that my stupid DVD player doesn't let me skip over FBI warnings and previews. The fact that it was designed that way on purpose, doesn't mean it isn't something worth complaining about.
I think it's funny you feel complaining about the complaining is important but the original issue is not significant in comparison.
I'm not complaining about your complaining - I don't think you should stop or anything like that. I'm simply voicing my opinion just like you are. It's all good.
On to your points. If I was upset at my phone's browser (and believe me, my phone's browser shouldn't even be called a browser) I would just look for a better phone, one with a browser I liked. Same with the DVD player. I don't think that's what we're talking about here though. It's more like your DVD player vendor was saying "you can circumvent the FBI warnings, but only if you do it while singing the alphabet backwards"... well, if I cared about the FBI warnings that much and had the time to spare and otherwise enjoyed that DVD player, I'd just do it the way they wanted. I just have better (from my perspective, of course) things to worry about than "HEY, they should let me remove those warnings while singing anything I want!"...
To get back to specifics and away from stupid analogies: It is true that I'd prefer to write an iPhone app in Ruby than in Objective-C. I just don't think that my preference is Apple's problem. They're just doing fine without me, after all. This could come back to bite them, but then again it might not. So I'm perfectly happy to agree to disagree here.
So to reiterate. I don't think this is not significant, just that it is not significant to me. I didn't mean for my comment to be taken literally as a "no, you should all stop caring", even if I came across that way.
> It is true that I'd prefer to write an iPhone app in Ruby than in Objective-C. I just don't think that my preference is Apple's problem.
I think we've touched on another disconnect. I don't think it's Apple's problem either -- it's our problem. We're still working out just how big of a problem this is for us. For you, the problem is no Ruby.
> This could come back to bite them, but then again it might not.
I don't really care if it bites them or not. I'm not trying to give them a friendly suggestion. I don't think they care. I just think it's a crappy thing to do.
Everyday I see iPhone this and IPad that. I think some people like getting abused by Apple.
Apple should do well to remember that they need us more than we need them. It's the availability of apps that makes or breaks any OS.
And you know what? In my country the iPhone is only popular with the tech crowd. Nokia is the leader here, and Vodafone (the largest mobile operator here and the direct competitor to Orange, which is shipping iPhones) is said to start shipping Motorola Droids and Nexus Ones.
This article is about 'Steve Jobs' 'going crazy' and doing this 'insane' thing preventing developers from using any old random dev environment to make apps for it's walled garden.
The iPhone isn't very popular where I live at all because the cell companies are crazy rip-off artists... that's has nothing to do with this.
Besides that, regular people (say, my mom) don't give a crap if I wasn't allowed to use ActionScript to write my app or not so what exactly is Apple doing to abuse people? Are they abusing developers? Well, they are limiting them pretty heavily, that's true -- but abusing? Hardly. As you said, Apple can 'fuck off' and surprise surprise that's exactly what Apple is saying to you (figurative 'you', the developer who wants to use AS3, say) - "If you don't like ToS you are required to agree to then don't agree to it."
There may not be an out-of-the-box solution for writing Erlang apps on Zune, but what if someone wanted to make one? There'd be no problem. They'd still have to compile down to something that Zune understands and that's all that's necessary. Cross-compilers and language-to-language compilers are a big part of computer science, they are cool and great, and it is none of Apple's business how you build your program as long as it doesn't cause trouble.
If Ford made "drives a Ford" a requirement for all of its employees, would that be fair? Couldn't you just say "they want you to use their stack"? It is totally evil.
Why does everyone act like the iPhone should be as 'open' as an OS on your computer? Did everyone forget that when the iPhone shipped you couldn't write apps at all? You can't write apps in Erlang for your Zune, your PS3, your cable modem, your microwave, your car or your apartments alarm system... no one cares.
Yes, Apple wants (insists, even, if this ToS becomes final) you to use their tools, their stack, etc for making apps on their consumer electronics device - shocking? No. Annoying? Of course. Don't like it? Go somewhere else!