2 ms·
I admit I haven't read all the comments. But what I have read from the author, in some comments here and in the follow up article, I get the impression that the
by Crenshinibon 12y ago
I admit I haven't read all the comments. But what I have read from the author, in some comments here and in the follow up article, I get the impression that there get things mixed up, that actually don't belong together. In my opinion you have to distinguish between web apps and content pages.
In the first, client side templating is just fine and the right way. Everything changes and the users are making a great deal of changing the output. A round-trip here is destroying the feeling of an app.
In the second, client side templating is just unnecessary. But so is server side templating, in many cases. Taken that the pages to display are rarely changed it would be even better to have simple static html, pre compiled.
The hard task comes when we have some mixed scenarios. A CMS for example. In my opinion the content creation process is a very valid use case for client-side-rendering - an app for creating html output, if you will. But when it comes to display that content it should reside precompiled (no server side rendering) on the server. So that just plain html pages have to be delivered to the actual users.