3 ms·
For a language whose nearly exclusive use case is writing Cocoa applications, it’s odd how Swift ignored most of what had made Obj-C so good for GUI apps. Inste
by pavlov 7y ago
For a language whose nearly exclusive use case is writing Cocoa applications, it’s odd how Swift ignored most of what had made Obj-C so good for GUI apps. Instead they just doubled down on everything that C++ was and Obj-C actively had tried to avoid.
- jzelinskie 7y agoWould you mind expanding on these feature sets a bit more? Because I just started playing with SwiftUI/Combine without ever using ObjC/UIKit, I don't know what parts of ObjC shined.
- saagarjha 7y agoObjective-C was a good fit for dynamic, object-oriented GUI frameworks like Cocoa because that’s how it itself was structured. SwiftUI and Combine are simply a different way of structuring UI code that fits a lot better with Swift’s strengths.
- solarkraft 7y agoCould you expand on that? How do the structures differ?
- deleted 7y ago[deleted]
- jcelerier 7y agoThat is the first time in my life I hear objc and good in the same sentence. Every UI developer I know who has worked in it actively despised it.