I am not primarily a front end developer but I am always intrigued by React as a way to develop UI (Its significantly better than having a separate XML). Severa

I am not primarily a front end developer but I am always intrigued by React as a way to develop UI (Its significantly better than having a separate XML). Several things that bother me right now is while working on personal projects involving React: 1. Generating unique ID for debugging purposes. Currently, I simply use the project directory "component-user-settings-name". 2. React claims "As a React developer, you focus on what you want the user experience to look like, and React handles how to deliver that experience"[1] but this is not always true. JS have something like COW memory management and AFAIK, React already requires you to make a full clone for each render (if the object changes) so you _really_ want to avoid them if possible. So you actually do care what React does internally thus I wonder if the COW semantic can be made clearer. 3. You sometimes have to do object of arrays instead of array of objects when you have a short list of very complex objects. The fact that I have to care about this is unfortunate, as refactoring from one to the other is not always straightforward, especially when you need to consider if you changes will cause JS to make clones. I also wish React can be transpiled/compiled into a much lower level language with clearer performance characteristics. I think Slint UI is the closest that I can find. [1] https://reactjs.org/blog/2022/03/29/react-v18.html https://reactjs.org/blog/2022/03/29/react-v18.html