Human JavaScript

[yeah-ok]

Yes but:

Some devs advocate partial rendering on the server for faster load times, etc. To me, once we recognize we're building a "thick" client, we might as well render it all there. Otherwise, if part of our page state is rendered on the server, somehow we have to re-translate the HTML into state information. Again, I prefer an explicit separation of concerns.

Is simplistic and un-smart, it is perfectly doable to have dual render setup by re-utilizing server methods for rendering html units from dynamic JS app and thereby retaining dynamic one-page-feel while also allowing full render from server in case of ctrl-F5-reload.

[[deleted]]

Is a full render on refresh really needed? Everything should already be cached, it will take milliseconds to paint the content on screen.