No, if they "dragged their feet" it was simply because Java's static OO-ness doesn't map well to Objective-C's fully dynamic nature. Objective-C is basically just Smalltalk semantics (minus control structures) bolted on to C.
It works surprisingly well, but you can't and won't believe it until you try it yourself.
Comments
No, if they "dragged their feet" it was simply because Java's static OO-ness doesn't map well to Objective-C's fully dynamic nature. Objective-C is basically just Smalltalk semantics (minus control structures) bolted on to C.
It works surprisingly well, but you can't and won't believe it until you try it yourself.
That's inconsistent with how quickly Apple had Carbon ready using C. Just a matter of effort.
Carbon is a port of C APIs from the classic mac mostly. On top of that, Objective-C is ultimately C, and its easier to talk between the two than Java.