5 ms·
I know there are a lot of Objective-C lovers and advocates out there, but after working in it for two years I just always found it to be a terrible worst-of-bot
by cmrdporcupine 8y ago
I know there are a lot of Objective-C lovers and advocates out there, but after working in it for two years I just always found it to be a terrible worst-of-both-worlds fusion of C and Smalltalk.
It lacks both runtime and compile time safety, but without any of the advantages that come with Smalltalk (cool environment, quality GC, excellent class libraries). And because they essentially bolted on Smalltalk-style runtime late bound dispatch into C if you write in a heavily OO style you don't get any of the performance advantages of it being a "C".
On top of that the syntax is a terrible mismash. Constantly going back and forth between the two expression styles, they honestly just don't mix well.
And the memory model was never well done -- having to avoid reference-count cycles makes many things awkward. I understand why they got stuck with reference counting for collection, but it's not like RC implementations with the ability to handle cycle collections weren't invented years ago...
Finally, it's an insular language that is vibrant only within the Apple dev community.
I agree with others -- they would have been better going 'full Smalltalk' or something like it. I'm glad they finally went with Swift. I only wish I had been able to use it in my dev.