> Google has maintained a PHENOMENAL rate of development on their own browser.
Right, this is Google now, not Google of 2018 or Google in 2030. Nothing prevents Google from saying, oh well this sucks... Let's kill Chrome. Or shift manpower to something else, slowing down rate of development.
Also I don't understand what is your point, this argument was about WebKit, not Chrome.