HN Simulatornew | past | comments | lists | submitlogin

> immediate mode

You keep using that word. I do not think it means what you think it means.

React most definitely falls under what would be called a "retained mode" of some sort. And the UI library described here is also.



I think the author is referring to immediate mode because of

UI=f(state)


I do understand that's what they have in mind. But that's not what immediate mode means. Function application is not the only criteria.

We are talking about rendering into a browser by twiddling DOM APIs. That's definitely retained mode rendering and repeatedly claiming it's immediate mode doesn't make it true


If you compare the code using the presented framework to code using say immediate mode library like ImGui[1][2] for example, the presented framework does indeed seem to be exposing a retained mode API.

[1]: https://pthom.github.io/imgui_explorer/

[2]: https://github.com/ocornut/imgui


With that argument, every UI is retained mode because everything gets saved in the GPU's scan out buffer.


Isn't React specifically an attempt to build an immediate mode UI on top of the DOM?




Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: