The web should be words and documents first (I think this page is worth reading http://justinjackson.ca/words.html). It's too late to say but if you want a sandboxed application platform, develop it out of the web. I still believe the plug-in was not a that bad idea, not the best idea though. At least you can disable it anytime and you have freedom of choice.
I suspect that the back button will be eliminated next. Because it collapses most web applications and "user experience".
If the web want to become a perfect application platform, all virtue of the web will be lost.
Web has always been about managing documents in one way or the other. Now those documents are interactive and interesting to watch and listen.
I mean, if my old chem book had cool animations I could tinker with I'd probably be having fun with it right now. I don't understand the outcry for GOW. It's still around and you can still make those sites, but they are usually hard to read (no fancy column layout to make it easy on the eyes) and you have to be a great writer to really engage the audience.
Going back to GOW won't make bad writters instantly better. No more than returning to 8-bit graphic won't instantly make all games better.
It didn't start out as lets make an application platform that can be accessed via url, it was make a document format (html) and share them over a network protocol (http) and provide scripting with javascript, and when everyone and their moms PC had that, developers started saying "can't we make that into a full blown application platform?" (besides failed experiments like java plugins or flash as an application framework)
I really wish we had just let html be documents and made a real remote-access application framework to work along side it, rather than having your program be 2 - 3 tags of html and 5MB of js. I'd much rather be sharing a qml application than an html5 one, because the latter was ground up designed to be a full featured interactive graphical interface program.
That would actually be neat, if browser engines included a qml parser and could load qml files as programs in the browser window frame. It is just extended javascript after all.
The idea is that JavaScript allows a relatively safe way to do that in a sandboxed environment (the browser) that is available on almost every computer.
The developers who really want the web to just be a bunch of static HTML are actually inhibiting that vision of a web platform. Because if disabling JavaScript were to become popular, that takes away that capability of web browsers to run applications. The conversation would go from something like "we can use JavaScript and this application will run for anyone who has a new version of Firefox, Chrome, or IE10/11, or Safari" to "we can deploy our application to the latest browsers, but we will have to first present a screen asking users to enable JavaScript on our site" or something along those lines. It goes from being a ubiquitous cross-platform solution to one that will only run for people who like JavaScript.
JavaScript in the browser is by far the best option we have now and in the foreseeable future for easily deploying applications across different types of operating systems and even devices.
Its amazing to me how many people don't appreciate that goal or really take it into account.