That&#x27;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&#x27;t use <i>any</i> JS (other than the Google Analytics hook), and it loads&#x2F;runs like a dream on <i>any</i> device&#x2F;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&#x27;s just time to bite the bullet and separate out the two use cases in a more forceful and clear manner.