<story><title>The Browser Company’s Darin Fisher thinks it’s time to reinvent the browser</title><url>https://www.theverge.com/2022/10/31/23428862/arc-browser-web-company-darin-fisher</url></story><parent_chain><item><author>Vermeulen</author><text>Reinventing the browser should be simplifying it to only what it needs to be: executing + rendering remote code in a sandboxed window.&lt;p&gt;Make a new browser that is just WebGPU + WebAssembly, no more DOM. Would already run the next wave of games that will come targeting that.&lt;p&gt;Then for regular websites, have them deliver a HTML rendering engine written in Webassembly for how they want to be rendered. No more need to test websites on a range of browsers</text></item></parent_chain><comment><author>paxys</author><text>Great idea, every website should write its own WebGPU-based rendering engine from scratch.&lt;p&gt;But that will be way too much effort for every kind of project, so what can really happen is some large players write engines and define interfaces for them, and we can all use them for our sites.&lt;p&gt;But different engines rendering the same data differently is probably going to be confusing (what if I want to swap them to compare performance?), so we should also standardize on some rules for how they do that. Maybe define some kind of document model and styling language?&lt;p&gt;Also, downloading all these engines on every page load might be too wasteful, so we can pick a couple of the dominant ones and bundle them into the browser itself. That way sites just have to send over structured content and the browser can load them all without a problem.&lt;p&gt;If we can ever get to this it will be a great web experience!</text></comment>
<story><title>The Browser Company’s Darin Fisher thinks it’s time to reinvent the browser</title><url>https://www.theverge.com/2022/10/31/23428862/arc-browser-web-company-darin-fisher</url></story><parent_chain><item><author>Vermeulen</author><text>Reinventing the browser should be simplifying it to only what it needs to be: executing + rendering remote code in a sandboxed window.&lt;p&gt;Make a new browser that is just WebGPU + WebAssembly, no more DOM. Would already run the next wave of games that will come targeting that.&lt;p&gt;Then for regular websites, have them deliver a HTML rendering engine written in Webassembly for how they want to be rendered. No more need to test websites on a range of browsers</text></item></parent_chain><comment><author>wruza</author><text>I don’t think this is a good idea. We’ll run into a situation with many different not-dom guis having the same set of problems that existing not-dom guis had for all these years. Think gnome-like drama for the half of the internet. Dom&amp;#x2F;css is no doubt a mountain of something stinky, but at least it is a slow moving standard and never had any politics or bdfl opinions involved. Also it has a set of features (e.g. accessibility, ad blocking) which would be hard to implement everywhere in the same way. Maybe something more low-level than dom but still integratable with higher-level apis and features could be built into a new browser paradigm.</text></comment>