Yes and no. I agree with the premise that React is done backwards, yet it abstracts away complexities of DOM manipulation and provides a templating language that is easy to read and write. I am a bit torn here - would love to throw away React and use something that gets things right, yet I am not willing to invest time to rewrite everything just because React happens to suck from a purist and perfectionist perspective.

The portal approach suggested just creates duplicates of everything and puts even more pressure on a small team to maintain 2 code bases, which will eventually turn into hell if the process of eliminating react doesn't move fast enough.

Drawing a line at route level and orchestrating some sort of microfrontends approach might solve an issue, but then the question is what is that issue we are trying to solve. I guess at some point we have to put business interests above framework wars.

Thanks for an engaging discussion. I have a love/hate relationship with React. Now that CRA is out, life is much easier, but then the direction that React is taking with version 18 makes me scratch my head and wonder if we should start laying some hay down to make the future fall a bit softer.