> I guess it would be possible for someone to add a layer on top of ImGui that would perform diffs on the UI model, similar to React. That would very likely be

> I guess it would be possible for someone to add a layer on top of ImGui that would perform diffs on the UI model, similar to React. That would very likely be done at a loss, the processing/clipping of ImGui is sufficiently fast. > I still think there's a lot of implementation details that leak out when you're coding (the stuff with the double hashes for instance) Yes the id-stack system is an artefact of the entire architecture but it's pretty trivial, transparent and a cost that is immediately amortized once you understand the UI architecture. Double-hash is a feature, would you prefer an UI system where every single widget would requires an explicit ID? Or worse, an explicit storage (like most RMGUI). Every piece of software involve implementation details. The details of QT can get pretty opaque if you ask me. I am bit annoyed with people just theorizing on performance issues that they haven't experienced themselves. I wish people where spending a tenth of the time looking at the cost of naively using std::string or containers.