> this almost comes off as some kind of obvious discovery they've made Except that it's not? We are currently in a weird path-dependent state for GUIs. Becau

> this almost comes off as some kind of obvious discovery they've made Except that it's not? We are currently in a weird path-dependent state for GUIs. Because GUI toolkits are such a pile of detailed work, it takes a lot of effort to create good general ones. The ones we currently have were all designed prior to ubiquitous 3D performance, have a strong dependency on object orientedness, and were often designed around constrained CPU and memory. None of this holds today. However, we still use the same toolkits. The immediate-mode GUI stuff is interesting, but throws away all OS integration which means accessibility is right out the window. Responsive GUIs (see: every DAW (digital audio workstation)) all throw away GUI toolkits and implement their own. Not to mention that 2D rendering with 3D hardware is NOT a solved problem. The NV_path_rendering extension is not available in Vulkan or DirectX, as far as I know. Text shaping is decidedly video card unfriendly. The number of "vector" renderers can be counted on one hand--and you don't need any hands at all to count the 3D native ones. I welcome all the experimentation in this space. I just really hope we get some convergence to something interesting soon.