One of the hardest things for me with SwiftUI is that it doesn’t let me be a perfectionist.
I find myself saying “well, that’s going to have to be good enough”.
Happened twice today, and that’s two times too many.
One of the hardest things for me with SwiftUI is that it doesn’t let me be a perfectionist.
I find myself saying “well, that’s going to have to be good enough”.
Happened twice today, and that’s two times too many.
@chockenberry I've found the same thing, and it's a mixed blessing.
It significantly deepens rabbit holes, making it FAR more work than before to actually dive into them to tweak some little thing or make something work "right".
And that increased gap between "leave it alone, it's good enough” and “put in a bunch of work to get it 'right'" also makes me take the latter path far less often.
And that leads to simpler, less-buggy, more-easily-maintained code in the long run!
@marcoarment @chockenberry even as a junior iOS dev, this is how I feel about SwiftUI. I can build stuff super easily. Which is amazing for a junior. But when I want to tweak it, it’s a dead-end.
But UIKit I found unnecessarily hostile as a junior. It didn’t really make sense to me.