Tim Bray wants to utilize the resources at the client side to lessen the load on servers:

I suspect there’s a huge system-wide optimization waiting out there for us to grab, by pushing as much of the templating and page generation work out there onto the clients. In particular, when you’re personalizing a page, assign all the work you can to the personal computer sitting in front of the person in question. Yeah, that cool, responsive AJAXy stuff is nice but maybe it’s the icing on the cake; the real win is making the Web run faster. ongoing doesn’t do any sexy-UI stuff, but you know, the page content could be a lot more dynamic, and there’s no reason for it to run slower; or even to upgrade from the single fairly-basic Athlon that hosts it.

That's a good idea, but it has one downside: the compatibility issue. I dropped a simple javascript html editor into my comment page here, and Mac users got up in arms over it - because the editor doesn't work with Safari. That's the sort of issue that any push like this will hit, unfortunately.