4 ms·
> When SwiftUI works it is a nigh-magical delight, but when it behaves unexpectedly or when behavior outside the prescribed path is desired, it can be difficult
by tambourine_man 4y ago
> When SwiftUI works it is a nigh-magical delight, but when it behaves unexpectedly or when behavior outside the prescribed path is desired, it can be difficult to understand and work around its limitations.
The author is being kind. Once outside the prescribed path, you’re in deep trouble. And that’s the thing with declarative code. There must be a great escape hatch. The framework can’t foresee all possible use cases.
- andrekandre 4y ago> There must be a great escape hatch. or you wait for the next os release (which really hurts adoption and dirties code with lots of workarounds)
- tambourine_man 4y ago100% coverage is impossible. That has to be recognized while still chasing that asymptote
- andrekandre 4y agoyes, definitely, though would hope they could do a better job of back-porting than current...
- spideymans 4y agoA lot of developers seem convinced that Apple will abandon UIKit for SwiftUI, but I just can’t see it happening for this reason
- pilif 4y agoThey will continue to use UIKit / AppKit for their own apps. They will just make it so that doing so will require a private entitlement. 3rd party apps will be restricted to SwiftUI. Apple is very much in the camp of maybe tolerating third parties, but only so long as they only ever do stuff in the bounds of what Apple wants them to do
- GeekyBear 4y agoApple has signaled that SwiftUI is where they are going and will continue iterating on it for many years to come. They are like old-school Microsoft in that way. Version one is certain to be incomplete, but they will stick with it over the long haul. Apple certainly has done a much better job of picking a development strategy and iterating on it than Microsoft has over the past couple of decades.
- tambourine_man 4y agoWhich is not hard, since Microsoft is all over the place and changing the message every few years for the past decades. Apple could really use some good competition, because Windows and desktop Linux aren’t enough.
- viktorcode 4y agoThere is. You can easily nest UIKit/AppKit inside SwiftUI and vice versa.
- tambourine_man 4y agoMore like barely possible, not easy, in my last experience. Granted, it’s been a while since I played with it.
- socialdemocrat 4y agoYeah, I looked up how it worked and decided this is too much magic, I am sticking with good old Cocoa. Also I don’t really like auto layout. It is springs and struts for me.