4 ms·
Same here. I'm getting ready to explore ML applications on Apple systems, but first, I need to finally get around to learning SwiftUI as a shipping app system
by ChrisMarshallNY 3y ago
Same here.
I'm getting ready to explore ML applications on Apple systems, but first, I need to finally get around to learning SwiftUI as a shipping app system (I have only been playing with it, so far. Doing ship work is an order of magnitude more than the simple apps that are featured in "Learn SwiftUI" courses).
I'll probably do that, switching over to using SwiftUI for all of my test harnesses. My test harnesses tend to be fairly robust systems.
So far, it looks like I may not be using it to actually ship stuff, for a while. Auto Layout is a huge pain, but it is very, very powerful. I can basically do anything I want, in UI, with it. SwiftUI seems to make using default Apple UI ridiculously easy, but the jury is out, as to how far off the beaten path I can go.
BTW: I have been "retired," since 2017. I wanted to keep working, but no one wanted me, so I set up a small company to buy my toys, and kept coding. I also love learning new stuff.
- ChrisMarshallNY 3y agoUgh. Just slammed into a wall. SwiftUI is very bad at working with maps, and they still have a long way to go. Since most of the stuff I'm doing, these days, is highly location-dependent, I can't compromise. I have been reading about people hitting these types of walls for a couple of years, and thought that Apple has worked around it. I suspect that the issue is with trying to use UIKit stuff inside of SwiftUI, and I was trying to avoid UIViewRepresentable (because it's a kludge). Back to UIKit. This stinks. :(