4 ms·
Follow a couple of rules and this won’t happen. Type annotate everything. Don’t mix integers and doubles, be explicit. Most important of all, do not ever make
by fingerlocks 11mo ago
Follow a couple of rules and this won’t happen.
Type annotate everything. Don’t mix integers and doubles, be explicit.
Most important of all, do not ever make a long chain of nested result building function calls with those stupid trailing untyped dangling {} closures, especially when the closure expects an implicit return of an opaque ‘some’ type.
What I’m saying is, don’t use SwiftUI. It’s a pee filled kiddie pool to attract JavaScript react devs with awful performance and semantics.
- deliriumchn 11mo agoWell apple themselves are pushing swiftUI and I suspect it will be the main (and only) approach as time goes on, even though its just a wrapper around "older" approach...
- rob74 11mo agoSo then, another language which has lots of features, but if you are foolish enough to combine feature A, feature B and feature C, bad things will happen? C++ sends its regards...
- an0malous 11mo agoThat sucks because I really like the semantics of SwiftUI over UIKit. Declarative, reactive code just makes sense for UI.