Quote:
Originally Posted by NovaScotian
(Post 457387)
Apple's strict terms of service for its iPhone SDK are receiving grumbles.
|
Everyone thinks they're smart and like to bitch, basically. You'll notice
most of the people screaming aren't developers, just pundits and self-important bloggers.
Quote:
Voice over IP apps that want to use the data connection will be blocked.
|
Who in their RIGHT MIND thought AT&T was going to allow VoIP over their data network? iPhones have unlimited data plans, and this would completely circumvent any non-unlimited calling plan. I think it's a miracle Apple was able to say that they won't block VoIP via wi-fi, honestly. I thought AT&T was going to force Apple to nix that.
Quote:
Only Safari can be used as a browser, all others are forbidden.
|
To provide a well-integrated third-party browser, Apple would need to make more APIs public. It takes time and work to design a public API. More importantly, they have to continue supporting APIs they make public. You can't have everything instantly
or all the time because you don't have an infinite amount of resources available to manage it all.
This is the same reason there are other limitations of the APIs available in the beta. (And the fact that it's beta, which means "unfinished; not final".)
Quote:
The SDK prevents Sun from following through on its Java port.
|
You make it seem like Apple wanted to stop Sun specifically, when that's pretty off-base. The infeasibility of Java on the iPhone is incidental to the design of the iPhone's sandboxing. The reality of the matter is that there are security and stability concerns that come with allowing a piece of code like Java to exist within multiple applications. Suddenly you are susceptible to problems that exist both within the shared plug-in and any code that interacts with the plug-in. A recent QuickTime vulnerability demonstrates this point perfectly. (Honestly, no one I know cares at all that Safari Touch can't use Java. No one. Not a single person. I'd wager that very few iPhone owners really care about this, and that the only people who do are the ones being REALLY VOCAL ABOUT IT on the Internet for ego and page hits.)
I actually think it's a
good thing that we won't see Java on the iPhone anytime soon. Aside from stability and security concerns, memory is limited and there's no such thing as VM paging in devices like this. Java is not known for being well-tuned for power consumption or performance in web browsers. Maybe in the future, though, it'll happen.
In the happy land of rainbows and unicorns, we all have every platform and there aren't technical or design limitations. I don't live in that world. Bloggers THINK they live in that world. Therein lies the difference.
Quote:
Aren't Apple's methods a bit like Comcast's content filtering, and Microsoft's IE antics?
|
No. Someone is bound to argue with me, but:
Comcast is actively denying users specific services, and is the only ISP available for many people. Apple has designed a telephone that no one needs to buy.
Microsoft is a convicted illegal monopoly, so the government monitors what they do. No one bitches about what the cell phone manufacturers do with their devices because none of them is an illegal monopoly. I don't see anyone whining that Nokia phones have such-and-such limitation. Anyone who seriously thinks the government is going to step in and regulate the iPhone is absolutely delusional and listens to Cory Doctorow way too much.
If you don't like the iPhone SDK, don't buy an iPhone. It's as simple as that. The cell phone market is alive and well, and there are
tons of alternatives.