That's fine, but there is still a place for JS-only applications on the web. For example, we produce a web application development IDE that emits JS-only appli

That's fine, but there is still a place for JS-only applications on the web. For example, we produce a web application development IDE that emits JS-only applications (HTML just bootstraps the JS). The things you can do with such applications are numerous, and are the backbone of a lot of SAAS offerings. However, our company web site doesn't use any JS (other than the Google Analytics hook), and it loads/runs like a dream on any device/browser. The point here is that there is a rationale for both modes of operation (content vs. application), and maybe, like another commenter noted here, it's just time to bite the bullet and separate out the two use cases in a more forceful and clear manner.