"They have no idea what century they're in and they'll defend themselves, violently, if necessary."
Ok, so I have to learn React. I've stayed as far away from it as I could, for as long as I could. My mind balks at the notion that I have to learn it just because everyone else feels they have to use it because that's what the "cool kids" at Facebook are using. But now that I am forced to learn it, I'll admit that it is a neat idea. But it also confirms my suspicions that it is the reason why I'm unable to successfully click on anything on Facebook (or anywhere else that uses React). React completely removes the concept of "document" and replaces it with components. That's an interesting idea and a useful approach to application development, but there's a problem: the browser has no idea that this is what React is doing. The browser thinks it's still rendering a document. It's no wonder everything is always jumping around, making it impossible for me to click on what I'd intended to click on.
If we're going to go down this path−which I'm starting to see the case for doing so−then I think the browser has to be re-imagined. We need a new kind of user agent that doesn't constantly shuffle things around because of an ever-changing "document" that no longer exists.