Have never developed on/for apple platform, so I have no clue. Apple makes setting up development so hard, I wonder what motivates developers to jump through all the hoops.
> Apple makes setting up development so hard, I wonder what motivates developers to jump through all the hoops.
Money to be made. And they have (had) nice API for most development needs. The actual distribution is a arduous though, mostly around the Review process.
Taken to an extreme, what's stopping us from going back to C? The security issues will be found and resolved, performance will be great and it will compile on all platforms that ever existed.
Maybe it's just because I'm more of a SwiftUI person, but in the example on the homepage, the event == 'Cancel' condition seems like a strange and fragile way to check if a certain button was pressed...
Well it depends on how you define it. We have done several re-skinnings. This migration is a transition from one framework to another, which we’ve never done before. The reasons to leave the old framework lie on several axes (eng, design, product, etc.)
I think there is a "ship fast" component here that should be adjusted. Product Management introduced weekly "stable" releases in March, no matter the content.
reply