The author of zortax’s blog compares Rust desktop UI frameworks by asking a practical question: when one value changes, what runs? GPUI’s notify identifies an entity, while a signal-based UI tracks which computations read a value. The argument is about where change information lives as an interface grows.
- Coarse updates have a cost. In the author’s 3,000-row test, changing one label takes 8.4 ms with cached GPUI row views, or 92 ms with plain elements. A hand-written equality guard makes an unchanged write far cheaper.
- Caching depends on state placement. A retained-view experiment saves 83% when each panel owns its state, but runs 11% slower with the same state in a shared model.
- Precision can shift work to app code. Isolating a GPUI badge requires its own entity, subscription, copied count, guard, and notification. Signals can express the derived count once and track its readers.
- Signals have their own costs. Run-once components need explicit reactive closures. One measured signal framework still spends about 14 ms on layout after doing only 0.01 ms of reactive work.
Shape state around the reads that need to update, then measure the entire frame. The author works on the competing zgui framework; these are medians from an unpublished, single-machine harness whose adapters have not been reviewed by framework maintainers.