First, I want to thank you for the deep dive into one of your grievances with React. I completely understand this wart in React, so much so, that I use it an in

First, I want to thank you for the deep dive into one of your grievances with React. I completely understand this wart in React, so much so, that I use it an interview question for frontend developers. This kind of "connecting" is where even more complexity has often reared it's head as the common "solutions" are using something like Redux. A trivial example of what you are trying to explain is like a shopping cart; where the cart exists in the header, but the button to add items to it may exist elsewhere. That said, >The great success of React is in enforcing a new kind of authoritarianism: it enforces doctrine by explicitly disallowing heretical code. I don't think this is a bad thing, after all the success of Rust is also predicated on explicitly disallowing heretical code that may have been commonplace in C. Constraints lead to more maintainable code, which is ultimately what frameworks these provide. I don't think your complaint is unique to React due to the fact it's HTML that influences that hierarchal design. That said, I'm not a front-end dev, and I my exposure to UI patterns is relatively limited; so I'm looking forward to your eventual book.