This discussion really highlights how SwiftUI's design encourages thinking differently about state and view updates. It’s surprising at first that all sliders seem to re-initialize or trigger closures on every change, but understanding that SwiftUI recomputes view bodies based on state changes makes it clearer why that happens. The idea that views are lightweight structs and that re-initializing them is expected helps reduce concern about performance—as long as heavy computations are moved out of the views themselves.

It reminds me a bit of how good platforms, like UniQumZorg, carefully organize their components and workflows to avoid unnecessary overhead. Their Voor zorgaanbieders section is a great example of structuring responsibilities clearly, ensuring each part knows its role and doesn’t do extra work unnecessarily. Similarly, their Over ons page gives transparency about who they are and how they operate, which builds user trust — something that developers should consider in app design too.

Overall, when working with state and closures in SwiftUI or any platform, it’s about managing dependencies smartly and separating concerns to keep everything efficient and understandable. Thanks to everyone for sharing insights here — it’s helpful to see these practical experiences.