Having any infrastructure controlled by a publicly traded corporation has enormous historical precedent to lead to the dissolution of that infrastructure for shareholder profit.
Once Google feels comfortable with doing so not allowing arbitrary routing in Chrome will be on the table to control what websites people visit. The only things stopping that is a feeble threat of state intervention or the threat of competition in the browser space reclaiming market share as a result.
They can, and probably will, take Chrome wholly proprietary at some point. Microsoft kowtowing to their engine is in their favor for now, but long term its in their business interests that Microsoft not have a browser anymore. That they present Chrome as the only option to users.
We can mire in the details of what a browser is, but for 99% of people Chrome is a program you run that shows you the stuff you want. The http, html, etc underpinnings are totally irrelevant. Chrome could be doing anything as long as it were showing the content the user of it expects. Google has already done this in the past with things like SPDY. I'm sure standards realize this - its why http/2 was a thing after all - that at this point if Google creates a new protocol it is de-facto required to become a standard because that is the only way for alternative browsers to keep pace with Chrome.
As such Google gets to dictate the future of hypertext. Not the users of the platform, not standards bodies formed to collaborate, the board of directors of a publicly traded US company.
Even if Google takes Chrome proprietary in the future, Microsoft and others can continue on their forks. That's the beauty of open source in this case.
As for SPDY, standards bodies like to "pave the cowpaths" so they codify existing implementations. Apple and Mozilla supported SPDY, it eventually became http/2 as you say, and then everyone dropped support for SPDY. This sounds like everything worked as intended.
> Even if Google takes Chrome proprietary in the future, Microsoft and others can continue on their forks. That's the beauty of open source in this case.
It won't help much if a huge part of Chrome's proprietary new future involves running on proprietary content as well. Just wait until Chrome has some special non-HTTP integration with "lightning fast AMP pages" that other browsers can't serve, or serves a lot slower.
Once Google feels comfortable with doing so not allowing arbitrary routing in Chrome will be on the table to control what websites people visit. The only things stopping that is a feeble threat of state intervention or the threat of competition in the browser space reclaiming market share as a result.
They can, and probably will, take Chrome wholly proprietary at some point. Microsoft kowtowing to their engine is in their favor for now, but long term its in their business interests that Microsoft not have a browser anymore. That they present Chrome as the only option to users.
We can mire in the details of what a browser is, but for 99% of people Chrome is a program you run that shows you the stuff you want. The http, html, etc underpinnings are totally irrelevant. Chrome could be doing anything as long as it were showing the content the user of it expects. Google has already done this in the past with things like SPDY. I'm sure standards realize this - its why http/2 was a thing after all - that at this point if Google creates a new protocol it is de-facto required to become a standard because that is the only way for alternative browsers to keep pace with Chrome.
As such Google gets to dictate the future of hypertext. Not the users of the platform, not standards bodies formed to collaborate, the board of directors of a publicly traded US company.