Thanks for the article, great insights! Just about confirms what I did already expect, but still very good to get some real facts from someone who’s not a dummy :)
But only because there is cut-throat competition in the browser world. Which is sadly declining and becoming a Google Chrome engine only world. So the seconds waiting for something could return.
Have you seen the Chrome Dev Tools? They push (excessively imo) hard on web performance. The real risk is vendor-specific APIs leading to lock-in. We're already seeing it.
TL:DR; use catalyst (AppKit support has many performance and stability issues). UIKit is getting better over time so hobby projects are probably okay, but production SwiftUI apps are a risk at best. Improvements are part of the OS, so your users will need to stay up-to-date.
"If you are curious about SwiftUI, please don’t let this stop your enthusiasm. It’s clearly the future at Apple and all these issues will be resolved within a few years."
Seems like a long time to wait
Depending on complexity it might already be good enough - in my experience it takes always a few years until something is really good - be it Apple or another vendor.
I waited switching from objC to swift until we got swift4.0 with a stable abi. I’ll do the same for swiftui and wait till it becomes matured enough. As you said, it is good for hobby projects but not good enough for business.