Absolutely, but conversely: the performance hit of the virtual DOM _should_ (and that's doing a lot of heavy lifting) be irrelevant in a well designed UI, because aside from initial load, most parts of the UI don't change for the majority of the lifetime of the app. Only tiny portions of the UI update at a time. The parts that do update can most definitely update fast enough on even moderately modern hardware (both desktop and mobile).

That does, however, require having properly designed your UI, with a knowledge of where the power of your framework of choice is. And that's where a lot of apps fail. Even something as simple yet critical as using vdom keys tends to (for various reasons) never register for many folks, leading to terrible performance.

That's a pre-optimization. React Native Web has been very performant for all my real world use cases.

I'd rather a small perf hit than have another code base for web. You get web for basically free when making a RN app.

That is for APPS you want your WEBPAGE to perform better, don't use a SPA, use Astro or something similar.

Might as well do everything in Assembly or C because it's faster right? Same argument. Development speed matters too.