It should stay close to what it is because it's fairly good at its job. To make it more than that would be to generalize it away from its job into some new job.

It should stay close to what it is because it's fairly good at its job. To make it more than that would be to generalize it away from its job into some new job. This violates single responsibility. We've already learned our lesson with that and HTML; thus was born CSS. Making a web standard for single page apps doesn't really seem necessary. Applications are by their nature different than web sites. A web site is a collection of content displayed largely as pages that are designated by a URI. An application is an abstraction over the page model that minimizes the transparent page/resource model with an opaque process flow model. HTML, as it stands, can be the V in MVC in either. Making it take on the M or C gains us little and stands to lose us much.