Sadly it also breaks a fairly common navigation flow in SwiftUI – having 2 navigation buttons on the same screen causes nav pushes to immediately pop back. Thi

Sadly it also breaks a fairly common navigation flow in SwiftUI – having 2 navigation buttons on the same screen causes nav pushes to immediately pop back. This does however show an interesting trade-off of SwiftUI: by being a more abstract definition of a view hierarchy, they can change out implementations more easily than before to further optimise in each OS release. I'm hoping that they're essentially going down the route of rendering SwiftUI directly to Metal, their graphics API, as I'd expect that to be much faster and less energy intensive.