GPUI state model questioned for complex desktop apps
What happened
A technical critique on the Hacker News front page on November 9 argues that the state models of GPUI and egui don't suit complex desktop apps. In a test, a 3,000-row list with cached views per row took 8.4 ms to update one label in GPUI, against 92 ms with plain elements. The author says update cost grows with tree size, not change size. GPUI's notify locates only the entity, not which field changed, and finer updates mean splitting labels into separate views, which cancels out the API's simplicity.
Written by AI from the coverage · updated 9 hours ago
Coverage
Follow the reports to see the story from different sides.
- Hacker News front pageA Critique of GPUI
一篇技术批评文章认为，GPUI 和 egui 的状态模型不适合复杂桌面应用。作者实测 GPUI 在 3000 行列表、每行缓存视图时改一个标签需 8.4 ms，写成普通元素则需 92 ms，成本随树规模增长而非变更规模。作者称 GPUI 的 notify 只能定位到实体、无法感知具体字段变化，精度提升需把标签拆成独立 view，反而抵消其 API 简洁性。
Heat over time
Heat now 8·Comparable peak 10（Nov 9 13:00）·Comparable change over 24 hours –
The trend only compares accounts observed without gaps, so its range may be smaller than the current heat. Hover or tap the chart for each hour; the left and right arrow keys step through it.