I can categorize some approaches for you, but you can't completely separate what is on the server from what is on the browser because the server delivers the information to the browser. However, I will start with what is commonly referred to as the "view". I have not worked with Ruby or .Net so I will leave those out, but they of course are alternatives.
Server MVC Full Page Refresh (almost all state is on server): Server side rendering of Markup (Spring, Struts, JSF, PHP) -> HTML5, Javascript [jquery, bootstrap], CSS [boostrap]
Server MVC Partial Page Refresh (still state on server but less, and more state on the browser): Server side rendering of Markup (Spring, Struts, JSF, PHP) -> HTML5, Javascript [jquery, bootstrap], CSS [boostrap] <-- Note the stack is pretty much the same but you can gain a lot by building a Single Page App. You actually see a lot of this is architecture in the form of one off injected pages on major websites, like Netflix, TurboTax, lots and lots of places. However, very few places have fully committed themselves to making their whole website a SPA because its just too easy to retrofit an injection here and there on top of their full page refresh. However, I believe everyone will be going SPA eventually. It seems that simpler apps with little need for state on the server are probably the best candidates for the REST service model outlined below. While larger very complex sites with complex user states and strict security requirements will become HTML injection SPA's.
Server REST service: Server side is stateless json services (no ss frameworks ideally*) -> HTML5, Javascript [jquery**, bootstrap], CSS [boostrap], JsMVC***