It's going to be interesting to see how this plays out. It's an enormous effort on their part, and for the users with all the API changes. But Dan's "Beyond Re

It's going to be interesting to see how this plays out. It's an enormous effort on their part, and for the users with all the API changes. But Dan's "Beyond React 16" demo simply was not compelling at all for me. With the focus on latency but no mention of bandwidth, it's really hard to understand the full impact on mobile devices. With TCP, throughput decreases as latency increases. Queue up too many requests, and the UI will get more disconnected, not less. Anyone that has had to work on an image gallery knows this all too well. Then you have SSR, and promises from render() that potentially swallow errors... lots of unknowns here. If all these efforts turn into a wash, or at best a subtle improvement at a cost of relearning React... people are going to be asking if it was worth it.