SwiftAnchor: Declarative UI Regression Guard

Yup. Been feeling the same for several years now, on all points.The performance is bad; the developer experience is bad (it's a moving target, not a stable point); it was done to chase a trend (reactive) and to boost other Apple platforms (macOS, watchOS, tvOS, and now visionOS) rather than because it was the right technical solution; the UI and UX it generates is poor; and Apple (but not only Apple) seems to have stopped caring about quality over the last few years.(On that last point, I decided to skip macOS 26 because of all the issues, but here's what I faced with their -2025 offerings: ht

> There are hundreds of thousands of apps in the App Store that are 100% SwiftUI. They are real. And they are very much "production grade"The first is a statement of quantity, the second is a statement of quality, dubiously supprted by the first.The Mac Settings app still lags between panes years after it was redesigned to look like iOS. I would think that if they had a viable way build a high quality and performant app with even relatively basic UI components (if they cared to do so) they'd do it for the 1 app that's deployed to every mac.SwiftUI does work in certain circumstances, and does w

I wrote something similar a couple years ago too after having a pretty bad time with swift ui and concurrency: https://medium.com/goodones/pareto-optimal-apple-devtools-b4...