That same thought occurred to me when I was writing it. The conclusion I came to was that if RIM is going to offer an SDK for Mac (or any platform for that matter), they need to do it in an integrated way, just like their competitors. I have no problem with NOT offering an SDK for a specific OS, but if you make the decision to do it, don't do it half assed.
I think it's less important how "good" an SDK is unto itself, and more important how good it is relative to it's competition. In this case you have to compare the Playbook SDK to Apple's and Google's because when developers are making decision about which platform to work with, they're going to be choosing between them.
Comments
That same thought occurred to me when I was writing it. The conclusion I came to was that if RIM is going to offer an SDK for Mac (or any platform for that matter), they need to do it in an integrated way, just like their competitors. I have no problem with NOT offering an SDK for a specific OS, but if you make the decision to do it, don't do it half assed.
I think it's less important how "good" an SDK is unto itself, and more important how good it is relative to it's competition. In this case you have to compare the Playbook SDK to Apple's and Google's because when developers are making decision about which platform to work with, they're going to be choosing between them.