8 ms·
That’s a slippery slope. We’ll eventually turn the browser into an OS. And more features = more surface area for bugs.
by moltar 7y ago
That’s a slippery slope. We’ll eventually turn the browser into an OS.
And more features = more surface area for bugs.
- kalleboo 7y agoIt's increasingly looking like our two options are either 1. Turning the browser into an OS (what Google is working toward) 2. Downloading an OS on each page load (What webassembly is working toward)
- mekoka 7y agoAn OS? An exaggeration maybe, but only slight. The browser is pretty much its own environment already. It's been the case for decades. It can display text, process a variety of media, and run programs (written in JavaScript). The main cause of frustration at this point is that, compared to other popular programmable environments (C, PHP, Python, node.js, etc), where some real focus is put into evolving the language along with a variety of primary development tools, people in charge of the browser's ecosystem seem to still be coming to terms with the programmable part of its identity. All the dilly-dallying results in community efforts that pile on top of each other to create all this bloat that is carried from one tool to the next framework.