Many now complain about the different display of code in different browsers, on their incomplete compliance with the standards. The time when all browsers will fully comply with the standards is still very far away. Perhaps if one simple idea is implemented, this time will never come. Web applications and even Web-OS are becoming more and more popular. But no one is going to move completely on them. One of the main reasons is the lack of access to your files when the Internet is unavailable. Recently, the idea came up - what if you make the browser itself a web application? To write its engine, for example, in Flash, to ensure that HTML is correctly displayed in it, to add the feature of storing bookmarks / settings on the main server - in fact, it is not necessary anymore. Then browsers on the user's side will not be needed at all - all that is needed for browsing web pages is a flash-player (or something similar if you choose a non-Flash) that will download the online browser from the server itself.
Pros:
Storage of all settings on the server - the ability to access them from anywhere, resistance to local OS failures
For updating it is enough to replace files only on the server. As a result, all users always have the newest browser version.
Less likely to be able to execute arbitrary code on the user's machine.
The ability to create on the cache server frequently visited pages to speed up the loading of really popular sites
It will be easy to collect statistics on the use of the Internet
Minuses:
Java Virtual Machine Implementation Difficulties
High communication channel requirements for the server
A big load on the server's processor when executing the code on the pages (the server will calculate everything that browsers are doing now)
When a server crashes, absolutely everyone is left without the Internet.
The opinion of the habra people about this is interesting. Is it possible in principle? PS: I'm not a web programmer, please do not be offended if the idea is not feasible in principle. ')