I disagree with this: "Although templating is the correct solution, doing it in the browser is fundamentally wrong." We keep forgetting that the decision of w

I disagree with this: "Although templating is the correct solution, doing it in the browser is fundamentally wrong." We keep forgetting that the decision of where to run the view logic depends on the environment. We have swung between cpu and bandwidth as bottlenecks in the last decades multiple times, and that's how framework moved between server side and client side mvc multiple times. No approach is radically different. We moved to thin client when browser were good enough; increase in bandwidth and smaller latency enabled rich client application, making the browser thick again. Handheld devices however are getting more common, so people are facing problems with all the logic and content being manipulated on the client. It doesn't mean the thick client solution is fundamentally wrong. Also it doesn't mean we have to invent new strategies and pattern to solve this. When you take a step back from the technology and return to the problem it was solving, it appears to me that we are just back at the thin vs thick debate, and as before this is not an issue of 'which is better', more of 'which is more appropriate to the topology constraints we have'