Good points. So, some people say, &quot;hey, let&#x27;s use a declarative language like XML.&quot; Problem is that you still need to decide what, when and how to display your model. So, we end up with tags or otherwise that are merely attempts to hide logic. &lt;foreach&gt;. Yeah, right.<p>You can go the other way...just put the logic in the controller to format data and otherwise build the model in a way that is cognizant of the view. But, then you&#x27;ve just &quot;polluted&quot; the controller with the view.<p>One approach at solving this is frameworks like Wicket, which (in spite of shortcomings) encourages the use of view components in a way that allows them to render a more organic model. Yes, you may write some Java to render specialized components, but you&#x27;re at least using the same language and being specific about writing rendering code that is also reusable.