3 ms·
Having programmed for 20+ years in both Smalltalk and Objective-C ( + implemented both + contributed to Squeak,..), I have to disagree with you there. For me,
by mpweiher 14y ago
Having programmed for 20+ years in both Smalltalk and Objective-C ( + implemented both + contributed to Squeak,..), I have to disagree with you there.
For me, the Objective part of Objective-C is very close to Smalltalk, same dynamic messaging model, same perform(Selector):, same doesNotUnderstand/forwardInvocation handling, same ability to capture and replay messages, similar dynamic typing in the "object" part.
Recent developments are a bit of a mixed bag, Objective-C blocks are a welcome addition, though the syntax is cumbersome, ObjC finally got SmallIntegers.
In terms of "feel", the two can be very similar, though some of the libraries admittedly have a very different flavor and a lot of the recent activity in ObjC land has been pushing more in the direction of Java, which is a loss.
In the sense of objects being a means of connecting parts, ObjC actually seems closer to what I understand as the Smalltalk mission ("recurse on the idea of computer") than current Smalltalks, because it is so much more adept at talking to the rest of the world.
Differences, yes: the image, no "become:", memory management (very mixed bag on the ObjC side, but ...).