@krzyzanowskim@thecommanderapp It'd be great to have an option for single-window.
When working with multiple projects + multiple sessions, it's hard to find the right window.
@radbar_1 You’re saying create a Boolean or enum that defines each state and update it when state is entered? Use that as a condition for any state transition? Sounds like that would work but a little annoying to have to manually keep track of the current state.
@dankuntz@pxlboy@observable It's hard to say in the abstract without knowing specifically what you're doing.
I will say, I'm pretty disappointed in the lack of investment, especially this year, with greater investments in SwiftUI, especially when it comes to performance and workarounds.
@dankuntz@pxlboy@observable Makes sense. The projects you’re describing push the limits of what the system was probably designed for. We’ve been able to lean on SwiftUI pretty heavily, but that’s partly because we’ve kept things relatively flat.
@dankuntz@pxlboy@observable Fair enough. It depends on what you're trying to achieve. So far, any performance issues we've been able to work around or have been a non-issue. Too many abstraction layers often keep us from moving fast (delivering user value), so we tend to avoid it unlecess necessary.
@dankuntz@pxlboy@observable Have you tried the new profiler for Xcode 26 to see if it gives any details on what’s triggering updates?
We still support iOS 16 so haven’t moved to @Observable yet. We’ve been 95% SwiftUI for about 3 years now.
@alexkehr It may be the all time worst and that’s counting the breaking glass fiasco lol. Who’s even running the company at this point?
How many times did he say “cool”?