I get it. My general point is that there's an imbalance between the method of application delivery and the importance of the application (or the frequency of us

I get it. My general point is that there's an imbalance between the method of application delivery and the importance of the application (or the frequency of use). The method that we have makes sense for frequent hopping between different documents on different sites and spending some minutes on each. As was the case with the original "web of linked documents". But now there's undue baggage and pressure and complexity imposed on application developers because on one hand they are developing sophisticated applications that people use daily for many hours. On the other hand they have to worry about the most trivial things like if some library of bundle file is 200KB or 1MB. Or worry if javascript is even enabled or not, if whatever CSS feature like flexbox or grids or whatever is supported or not. A trivial thing turns into something complicated because you need fallbacks and polyfills and fallback for your fallback and you know the rest. It hurts the developers but also the users because time and effort that could be spent on the product is spent on this kind of stuff. That's why I think the separation of content and application is becoming more important. If you want snappy media that is not bloated and responsive and readable and open and all that fine. But if you want a full-blown CRM or spreadsheet or customer support desk software and the like that you spend your day on let's give the developers a break and give them a predictable environment with a robust method of application delivery, without bean counting the bytes, and empower them to focus on the real problem that they are trying to solve for you.