undefined | Better HN

0 pointsflagrant_taco2y ago0 comments

Exactly, 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.

0 comments

3 comments · 1 top-level

charcircuit2y ago· 2 in thread

>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_tacoOP2y ago

I 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.

charcircuit2y ago

Your 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.

1 more reply

j / k navigate · click thread line to collapse