>"competing engines would be good for the web"?
They will.
Citation needed. Because, to support my argument, we just saw a "competing engine" starting to divert from the others. And not only in this case -- just the other day the Google team announced they'd drop CSS Regions too.
Would it be as easy for Google to do so, if they were still sharing Webkit code with all the other Webkit partners?
>IE caught up already, and I don't see any evidence that it's "limping
Well, we still have to support IE10 (some also IE9). Everytime, every version gives something new, but holds something back that the latest other browser engines already have. E.g IE9 and WebGL.
>Webkit is not updating that fast anymore.
Well, there are fewer contributors now. But it's kind of hard to draw any conclusions about how fast it's updating given how little time has passed since Blink forked.
Nope, also before. Google had published commit stats in the time of the fork, and Apple had considerably slowed down commits for couple of years or so before that.
Citation needed. Because, to support my argument, we just saw a "competing engine" starting to divert from the others. And not only in this case -- just the other day the Google team announced they'd drop CSS Regions too.
Would it be as easy for Google to do so, if they were still sharing Webkit code with all the other Webkit partners?
>IE caught up already, and I don't see any evidence that it's "limping
Well, we still have to support IE10 (some also IE9). Everytime, every version gives something new, but holds something back that the latest other browser engines already have. E.g IE9 and WebGL.
>Webkit is not updating that fast anymore. Well, there are fewer contributors now. But it's kind of hard to draw any conclusions about how fast it's updating given how little time has passed since Blink forked.
Nope, also before. Google had published commit stats in the time of the fork, and Apple had considerably slowed down commits for couple of years or so before that.