-
It pretty much manages memory for you with ARC, the only thing you have to look out for being instance-loops where A retains B and B also retains A. It has closures (blocks) as a basic language type, and it is a true superset of C (unlike C++) so any C program will compile with the ObjC compiler. It also integrates with C++ for that matter.
Apple has invested too much in Swift for it to back down now, and I see some documentation is now Swift-only, not ObjC, so the writing is on the wall, but equally Apple has an enormous amount of internal code in ObjC, so it's going to be a long time before support goes away entirely.
And then, I'll just move to Linux. I've already written a basic implementation of a lot of the parts of Cocoa [1] with an SDL3 back-end, you even get GPU/compute shaders :) and although it's not ready for prime-time (the fit-and-finish needs some attention) it is the basis for me ultimately not needing to use Swift in future, a decade or so down the line, the bonus being that it'll work on anything - I have a proof-of-concept for it running on Windows, and GNUstep on Linux ought to make it easy to port there.
[1]: https://github.com/ThrudTheBarbarian/Azoth
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
You should check out Darling if you like Objective-C and Apple/macOS development. It is implementing a macOS translation layer on Linux. There is lots of work needed implementing Apple’s frameworks in Objective-C.
https://www.darlinghq.org/
-
Ugh, yes, I could not wrap my mind around QML either. I've dabbled in SwiftUI as a hobbyist and find it generally easy to use, though I do agree that the traditional Storyboard approach is easier to wrap my head around (also an amateur hobbyist there, with emphasis on amateur).
My experience is that iteration and development speed in SwiftUI is noticeably faster, but once your app reaches some level of stasis and maturity, the Storyboard approach is more robust and easier to manage and understand. I have some thoughts on why but we'll save that for another day.
My favorite UI framework as a developer is egui [0] with Dear ImGui [1] in second place.
Unfortunately, Dear ImGui is ugly as sin. egui is decent enough.
My understanding is that SwiftUI was Apple's direct response to React/Vue.
[0]: https://github.com/emilk/egui
[1]: https://github.com/ocornut/imgui
-
Ugh, yes, I could not wrap my mind around QML either. I've dabbled in SwiftUI as a hobbyist and find it generally easy to use, though I do agree that the traditional Storyboard approach is easier to wrap my head around (also an amateur hobbyist there, with emphasis on amateur).
My experience is that iteration and development speed in SwiftUI is noticeably faster, but once your app reaches some level of stasis and maturity, the Storyboard approach is more robust and easier to manage and understand. I have some thoughts on why but we'll save that for another day.
My favorite UI framework as a developer is egui [0] with Dear ImGui [1] in second place.
Unfortunately, Dear ImGui is ugly as sin. egui is decent enough.
My understanding is that SwiftUI was Apple's direct response to React/Vue.
[0]: https://github.com/emilk/egui
[1]: https://github.com/ocornut/imgui
