2 ms·
I'm a longtime fan of Cocoa and Objective-C. AppKit has pretty much paid my bills for the past 15 years. The reason I like Obj-C is the simplicity. You've got
by pavlov 8y ago
I'm a longtime fan of Cocoa and Objective-C. AppKit has pretty much paid my bills for the past 15 years.
The reason I like Obj-C is the simplicity. You've got C, the most popular and widely deployed programming language in the world with libraries available for pretty much everything. Then you add a minimal slice of proven Smalltalk constructs on top, completely orthogonal to the base language. There's rarely a question about whether you should be doing something the high-level object-oriented message passing way, or the low-level C "functions & struct pointers" way. The two play together with no surprises (unlike C++ which is a minefield of surprises for the C programmer).
Swift threw away the Smalltalk-like simple dynamism of Objective-C. Instead it gives you syntax that's got more sprawl than Scala; a swamp of type system combinatorial explosions that can rival C++; language instability on par with modern JavaScript; and the coup de grâce is that all this is connected at the hip to a giant framework that doesn't feel Swift-native because it's actually an Objective-C API with decades of baggage.
At the same time, Apple likes to pretend that Swift is a beginner-friendly language. It's a floor wax and a desert topping — and after you've iced the cake with a thick layer of Swift you can apparently both have it and eat it.