I remember when swift charts launch, a friend of mine was in tears because it launched 3 days after he painfully completed a UIKit project which had charts in it , getting its data from a raspberry 😂😂
People who don’t have a lot of multi threading experience may not realize just dumping everything on a mainactor thread has large implications for latency and responsiveness. It’s easy to block threads by accident. I’m curious how all this will work out.
are there resources to learn more about multi threading and performance? I was shocked when I realised a side project was using 468MB of RAM, all it did was get data from an api and display it
@@SanusiAdewalelet me know if you find anything too :( all I know is that UI changes go on the main thread and everything else doesn’t get priority as far as I know
@@riken2567 I think the general recommendation is, if you want a job *today*, then learn UIKit, but if you want to build your own apps from scratch, then SwiftUI is the way to go. SwiftUI will also help you build for all platforms from watchOS, iOS, visionOS to macOS.