Why plural? Probably "the web browser" is more correct term these days, no? The idea of "browser as OS" or "OS as browser" is not that new. That move started b

Why plural? Probably "the web browser" is more correct term these days, no? The idea of "browser as OS" or "OS as browser" is not that new. That move started by "active desktop" concept on Windows 95 (https://en.wikipedia.org/wiki/Active_Desktop https://en.wikipedia.org/wiki/Active_Desktop). And speaking about browser... It's main goal is to serve following tasks: 1. To provide safe browsing experience. 2. To present content to the user. Note that the order of these two tasks matters. Initial active desktop effort has died because order of these two tasks was wrong at their first attempt. From that point of view, "browser as OS" just increases attack surface. And so more and more isolation layers will be added into browsers making them less effective and performant than alternatives. Consider WebAssembly for example. That was desperate move to provide an option to run some computation-heavy code inside browsers with at least comparable speed of native code. But it always be slower than native solutions. Java vs native code, we've been there, seen that. To be short: native OS and solutions will always be more performant than the one emulated in the browser. Just because of the order of tasks. In this sense the browser will never be complete. It may become asymptotically close to the OS but will never reach that point. And note the price: on that way it will become asymptotically close to the size of OS.