The issue is you need some of both for an "optimal" solution.
Unfortunately, Javascript and the basic "controller" capabilities of a web browser just aren't up to the task.
Here are your "controller" options:
1) the server is the controller
2) the web page is the controller of itself (which sucks)
When what is probably needed is:
3) a controller that lives as an extension of the browser.
Frames, for all their issues, basically enabled #3. A controller frame could manipulate the view frames, and those frames were scoped/contained web page "processes". There were issues of course, if you hard-refreshed the overall page (and the "controller" frame) it would lose state, so I don't want to say that frames were a complete solution.
Client storage is half of the equation, and that was added. Good caching infrastructure, multiple asset delivery, connection multiplexing, that seems to be working so you don't need a "big bertha" first page. Standardized DOM capabilities and the like seem to be fairly well solved, and maybe the "Javascript problem" will be solved once ... crap the thing where you have an IR bytecode so you can code in anything in a browser... well that will be solved.
Frankly this needs to be solved. Apps and app stores are a pox upon the land, and the web browser can still save us from that.
Unfortunately, Javascript and the basic "controller" capabilities of a web browser just aren't up to the task.
Here are your "controller" options:
1) the server is the controller
2) the web page is the controller of itself (which sucks)
When what is probably needed is:
3) a controller that lives as an extension of the browser.
Frames, for all their issues, basically enabled #3. A controller frame could manipulate the view frames, and those frames were scoped/contained web page "processes". There were issues of course, if you hard-refreshed the overall page (and the "controller" frame) it would lose state, so I don't want to say that frames were a complete solution.
Client storage is half of the equation, and that was added. Good caching infrastructure, multiple asset delivery, connection multiplexing, that seems to be working so you don't need a "big bertha" first page. Standardized DOM capabilities and the like seem to be fairly well solved, and maybe the "Javascript problem" will be solved once ... crap the thing where you have an IR bytecode so you can code in anything in a browser... well that will be solved.
Frankly this needs to be solved. Apps and app stores are a pox upon the land, and the web browser can still save us from that.