3 ms·
Google's browser engine is open source. You can reuse Google's browser engine meaning that you can focus on the features that differentiate your browser instead
by charcircuit 3y ago
Google's browser engine is open source. You can reuse Google's browser engine meaning that you can focus on the features that differentiate your browser instead of implementing the spec like you suggest.
- dmarcos 3y agoYes. I see chromium as the linux kernel. Piece of fundamental infrastructure that does the the heavy lifting and one can reconfigure, tweak, add features or eventually fork if needed. Never been easier to build an independent browser.
- flagrant_taco 3y agoThe open web is dead if the only option is to base every browser on a Google core. How do specs fit into this if every browser is just a UI shell around chrome? Where is the competition driving innovation of the web platform when the only competitive landscape is how pretty you can make your toolbars and bookmarks? We need independent groups of passionate people making sure that the web platform is focused on the best end user experience. We don't always have that today, but that vision is completely dead if the web functionality is decided entirely by an advertising platform.
- charcircuit 3y ago>How do specs fit into this if every browser is just a UI shell around chrome? The browser engine is open source. You can make changes and proposals with your own fork. If you are making a browser for musicians you could try and advance the WebMIDI spec and add new functionality to it and then try to get it standardized. But as a browser developer you don't want to me spending your time implenting specs that other people have already implemented, but rather spending time working on things that improve your browser for your userbase.
- flagrant_taco 3y agoWhat you're describing is the opposite of the whole point of specifications. The aim wasn't to circle around a single implementation, it was to define feature specifications that would allow multiple vendors to build cross-compatable web browsers. What would be the point of open specifications if there was only a single implementation?
- charcircuit 3y ago>What would be the point of open specifications if there was only a single implementation? I never said there was? When you write the first implementation then there will only be a single implementation, but that's how counting works. 1 comes after 0. Anyone is free to write another implementation.
- dmarcos 3y agoKeep in mind that when using chromium you can innovate on any part of the stack not just the UI. You can focus on what matters to you: You can reimplement CSS animations, the network stack, add any new APIs, define any privacy or security policies… A robust and reusable browser engine lowers the barrier of entry for anyone to innovate and differentiate. Browser compatibility is close to solved since everyone shares most of the implementation. Better user experience across the board at lower cost. Specific examples are Brave, Opera, or more recently the Meta Browser shipping in the Meta Quest: very small team now leading the WebXR standard. it wouldn’t be possible without Chromium.
- fabrice_d 3y agoWhat if you need changes at the engine level to differentiate your browser?
- charcircuit 3y agoThen you make the changes to the engine. You are permitted to keep those changes to yourself if you wish.
- flagrant_taco 3y agoExactly, in that model the only way to build a browser is to depend on someone else to implement the specs. It's not feasible to build a new browser, at best you can start with what Google implemented, including proprietary features, and go from there. At that point you likely don't understand the codebase fully and are going to be dependant on staying in sync with chromium to get new features. This model of starting with chromium really has nothing to do with building a web browser, it is just building a UI around Google's browser. There isn't much daylight between that and the often complained about limitation of Apple only allowing the use of WebKit on iOS.
- charcircuit 3y ago>At that point you likely don't understand the codebase fully It's faster to learn the part of the comebase you are interested in rather than building a whole browser engine. >and are going to be dependant on staying in sync with chromium to get new features. Being able to reuse the work Google is investing into th browser engine is a positive. >There isn't much daylight between that and the often complained about limitation of Apple only allowing the use of WebKit on iOS. The difference is you can make changes to the browser engine if you need.
- flagrant_taco 3y agoI think we're just thinking about very stiffener goals for the web. I'm not interested in a version of the web that is driven by one browser or company, even if it can technically be modified or tweaked as long as you don't diverge see enough to break upstream compatibility.
- charcircuit 3y agoYour original comment was about competition between browsers. For browsers to compete they don't all need to have their own browser engine written from scratch. Web standards are not driven by one browser or one company. That would still be true if everyone based their browsers off of Blink.