Nycturne
Elite Member
- Joined
- Nov 12, 2021
- Posts
- 1,551
Except this isn’t even a rebuttal of my statement. The developers who went Electron/ReactNative skipped over Swift entirely for the most part, assuming they ever wrote Objective-C against UIKit at all. SwiftUI is a response to React and similar frameworks to provide something more familiar to that sort of developer.
Swift has gotten complex, partly because of the language additions, and partly because it now enables DSLs like SwiftUI (to compete with JSX). The more I work with DSLs, the more I find them to be a mixed bag. But it has been a pretty painful transition dealing with language-level async in Swift IME.
This feels like a grass is always greener moment. As someone who spent a bunch of time doing React Native on mobile, it’s got its own problems, as does React. The larger the project, the more pain I’ve had with the JS world. I don’t miss package dependency hell when I can get back to native development.
If by replace you mean "still use UIKit for events and providing a drawing canvas to hook into", sure. But you can’t get away from the fact that it is UIKit that gives you your UI events (keyboard, finger, etc) and provides a CALayer to draw into if you want to go that route yourself. And about the only folks willing to go down this route are teams that already have a UI framework they are willing to port, like Google.
