Yeah, god, I long for the days before Google Maps, too. Who needs that slick slippy interface when you can endlessly click arrows at the corner of a static image?
It is a long term evolution. Eventually, application developers will build directly atop the accelerated graphics layers, freeing the browser to be just a basic virtual machine, and leaving HTML rendering to be just another app built atop that machine. But these things take time and there is a lot of legacy cruft that needs to work in the meantime.
Care to elaborate? That is not the direction I pictured at all. The open standards of the web should have the opposite effect, allowing anyone to build a computer that can run the major software offerings of the time.
I do not see it really any different to how web applications are developed today, just throwing out the needless overhead. If your concerns are to be realized, it has probably already happened a long time ago.
For one, whatever Tim Berner's Lee envisoned, the web is not the simple mostly textual medium it was in 1993. Get over it.
Second, for people to love reading text on the web, there was never a better time than the present. Lots of long form text by bloggers and content providers like Medium etc, combined with a widespread interest in improved readability and good typography. Plus, the fashion/preference for "minimalist" designs also helps putting emphasis on the content, even better than some 1997 site with animated gifs and black text on grey.
The universal reply to "get over it" is "if it's a problem for me, then it's a problem". Are you sure there's no grain of truth in the complaints about today's dynamic Web? How about this critique, which is hopefully more articulate? http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-Nov...
IMO, browser plugins were the way forward. You can have all the fancy stuff that modern computers can do, like Google Maps or even Quake Live, and at the same time most of the web can stay simple.