3 ms·
Good luck with supporting Mac GUIs. It's a constantly shifting target. Carbon is gone, but now Cocoa isn't always Cocoa because you also have to support SwiftUI
by teilo 5y ago
Good luck with supporting Mac GUIs. It's a constantly shifting target. Carbon is gone, but now Cocoa isn't always Cocoa because you also have to support SwiftUI, which is itself a moving target.
- Uehreka 5y agoI thought SwiftUI was an abstraction layer on top of Cocoa, Cocoa Touch, etc. so you could reuse code between executables. Is that not the case?
- teilo 5y agoIt is, but perhaps I'm not understanding how it is currently implemented. I thought there was a system framework it relied upon, and if so, that framework would need to be implemented in Darling. Perhaps the framework is embedded in every .app package? There's a similar issue with the Swift runtime. I believe Apple's goal is to make it a system framework, at which point it would also need to be implemented in Darling.