Isnt this something the OS should handle and Chrome just uses the OS interfaces for this?
Isn't QUIC something an OS should provide?
Isn't the OS responsible for preventing antivirus software installing insecure browser plugins?
Isn't the OS responsible for process sandboxing?
Isn't the OS responsible for secure font rendering?
Isn't the OS responsible for shipping with decent optimized image and movie decoding libraries?
The innovation must be pushed somewhere. These days it's being pushed by the browser vendors and not OS vendors.
the problem is, how can chrome+firefox persuade microsoft, apple, debian and redhat to add it? and how long will that take? maybe some of them don't want it at all.
with the current approach they can offer this improvement to their user right now.
It should teach that Evergreen Browser requires Evergreen OS. And there is long tail.
Windows XP (2001) support:
* Internet Explorer 8 (2009) * Chrome 49 (2016) * Firefox 52 (2017)
IE supported latest versions only, should have been most integrated and now it's dead.
Given that whole UI and windowing toolkits are moving into the browser, that argument of replacing chunks of the OS, from top to bottom, starts to become more relevant (if not more comfortable).
And then the next step could be to have Google as a compulsory proxy for all web traffic, because of government blocks.