3 ms·
> "4) Dev tools that people are familiar with." This is a nice-to-have, and has IMO no bearing on the success of a platform. How many devs knew Obj-C well befo
by potatolicious 16y ago
> "4) Dev tools that people are familiar with."
This is a nice-to-have, and has IMO no bearing on the success of a platform. How many devs knew Obj-C well before the iPhone SDK came out? How many do now?
It's a bitter pill for developers to swallow, but the truth is that consumers drive platform adoption, and developers will learn whatever it takes to have a crack at the goldmine. Nokia went well out of its way to be dev-friendly, but couldn't produce a platform consumers wanted. Having a solid dev platform that's easy to use is good, but makes little difference when nobody's wielding your phone in the first place.
> "2) Existing tie-in to blackberry servers."
Doesn't last forever. The consumer preference for iOS and Android device is so strong that enterprises are starting to decouple themselves from BB enterprise servers. There's a difference between the bitchings of rank and file engineers and the CEO being unable to use the new fancy sexy device because IT doesn't support it. One gets more change than the other, sadly.
The tie-in to RIM's proprietary servers is a stopgap at best. Without it RIM would be sinking far more rapidly than they already are. It is an advantage that is shrinking and won't last for much longer.