Websockets are of use to live documents. Application stacks are different. The definition is extremely important as the current level of interaction richness

Websockets are of use to live documents. Application stacks are different. The definition is extremely important as the current level of interaction richness was never really envisaged in 1996. A document is a resource that is available specifically over http or https. An application is something entirely different as it can be served via a huge array of protocols and terminated and rendered entirely differently. The separation of concerns here is my need, not the terminology. For example, how much time have programmers spent globally repeatedly creating and implementing a user login and password reset flow? This is simply not the concern of the Document Object Model and it means that we have to put up with a huge array of home brewed solutions that each have their own weaknesses. Imagine the same effort and logic applied to routers or tcp/ip for that matter. The internet would simply not work or break. My point is - there has been a land grab over the UI / UX space that has meant standards like web components are marginalised in favour of 'frameworks' and compilers. Seems like an awful lot of duplicated effort to reach the same result.