A SwiftUI retrospective points at Apple's own Landmarks tutorial rendering a broken sidebar on current Xcode and macOS, unchanged for over two years

Sources: retrospective, HN discussion, r/swift thread
Summary: A retrospective on seven years of SwiftUI argues the framework has stayed mediocre, and grounds the argument in specific checkable defects rather than general complaint. The lead example is Apple's own Landmarks tutorial rendering a broken sidebar on current Xcode and macOS, unchanged for over two years. The structural argument of the piece is that back-deploying the framework as a dependency, the way Jetpack Compose ships on Android, would remove most of the availability-check churn in SwiftUI code.
Why it matters: Availability checks against OS versions are the cost SwiftUI imposes on every codebase that supports more than the newest release, and the piece names a shipping model that would remove them rather than a preference about API design.