I don't know, I'm still vaguely optimistic that people will realise that breaking the HTML/HTTP document model is causing more issues than it solves. Although we are going to need to address the issue of rendering dynamic content, since as of now HTML allows no real separation between content and representation. This frequently means that even if the content can be read from an HTTP endpoint then it still can't make it into the page without large blobs of JavaScript, just because the way the data is represented is different from the way it's read.
What makes you so sure it is causing more issues than it solves? We can do a LOT of things in the browser that we can't do with the pure html document model.
More isn't necessarily better. I'd rather have a simpler and more restrictive model with fewer performance, accessibility, maintainability, and security issues.
We have marketing to thank for that. Consumers don't care about performance because they're trained to buy $800 devices every year or two. They also don't care about security because being hacked is seen both inevitable and no big deal. And why should they care about accessibility? Most people don't need that at all.
It's not that people don't care, it's that in their eyes these are reasonable trade-offs for the rich capabilities offered by things like google maps, youtube, gmail etc.
Im all for getting rid of some of the cruft that has developed over the years, but let's not forget the literally world-changing utility that is enabled by the modern web.
Well, the fact that people are gradually moving towards REST APIs (sometimes even on the public facing side) at least suggest that some people clearly think that breaking the HTTP model was a bad idea. And I'm seeing increasingly many people that get annoyed with the bloated HTML pages that don't work without huge amounts of javascript and which break normal things like history or sometimes even scrolling.
Unlike the post I was replying to I'm not so much complaining about webpages that mimic (or are) standalone applications, I'm mostly complaining about webpages that have effectively built their own browser just to display some HTML documents.
Sure some stuff can't be done with a pure HTML document model (at least not without some kind of black-box html element), but plenty of stuff is just displaying some representation of content and (optionally) allowing people to manipulate it which really shouldn't require anywhere near the amount of effort people sometimes throw at it.
