Some valid points, but the compiler isn't Xcode and Swift isn't able to check the expression. Imho in these cases it's the developers lack of insight into how SwiftUI works, but otoh Apple often doesn't help with obtaining the insight..

They will also silently stop supporting some piece of library you rely on, leave it broken in some way or another, and just leave you on your own.

However, it has its good sides. The profiling tools are great for example. And I would rather work on 10 difficult problems with Xcode than on 1 with Visual Studio..

Thank you for sharing this, now I feel less dumb. Recently I had the pain of publishing my app (Flutter/Dart) on the apple Appstore, admittedly, my first experience using a mac in the last 30 years so I don't speak mac at all, but like, I know computers right?... famous last words.

I thought I was "holding it wrong"... like really badly wrong! and all I was trying to do was clone my repo and compile it for the store, that's it. took me nights and nights to get over each subsequent hurdle and false peak and missing import and then at the end, oh please upgrade and start again.

Thank goodness I only need it for that 1 step and I can do everything else on computers and software that is normal for me. As a first time app maker, I've had a super experience with Flutter in VScode.