The JSX is not the same as it is encapsulated in the render() method withing the JS file. This is the whole point of why this implementation is not a separation of concerns. The view is essentially embedded in the controller in order to simplify how a controller passes scope to the view.<p>This isn&#x27;t the first time people have fallen prey to embedding HTML as a string into JS to write the DOM.  5&#x2F;10&#x2F;15 years ago, if we saw this, devs would just shake our heads.  If anything React is an old hack, an anti-pattern brought forward again.<p>I misspoke about views in business logic, as you said, it is the controller logic, which should be decoupled from the view itself as well.  The naive example of converting a webcomponent to a JSX component may look similar, but more complex components will only require greater complexity for the render() method to handle.<p>I understand your rationalization, but the crux of the arguments here are concerned with the anti-pattern React introduces and why developers who&#x27;ve come across this before have seen this as technical debt. The arguments for React are a matter of opinion, wherein the arguments against it are based on the practical principles for programming UIs, principles have been forged to be tried and true since the 70&#x27;s.<p>I personally favor standards, such as webcomponents and OO programming for modules. I understand that this may not seem popular at this point and time, but 20 years of dev experience has taught me otherwise.