When the parent says view, they&#x27;re not talking about &quot;a) markup&quot;, they&#x27;re talking about the thing the user is looking at.<p>&gt; b) ids that indicate that a given tag will be replaced with a component<p>With that in mind, your disagreement is contradicted by this statement because logic has just been described to update the view.  Logic is necessary to generate a view of the data for the user.<p>With JSX, keeping all of this code closer together that is intrinsically tied together increases cohesion, by definition.  Subjectively, this makes it easier to manage UI because one only have too check one place for all the pieces.  For further exploration of this idea, check out the intro of this video on separation of concerns vs technology. [1]<p>On a separate point, it sounds like one must imperatively update the UI with Wicket, which is objectively more complex than what React affords, which is stateless UI.  Time is removed from the equation, which also makes things easier to reason about.<p>[1] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?time_continue=275&amp;v=x7cQ3mrcKaY" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?time_continue=275&amp;v=x7cQ3mrcKa...</a>