Then I stopped sucking and looked up stuff from the article.
Blink is a part of the chromium project, and is equivalently open[fn:0]. So that means it's equivalent to any other open source fork.
Mailing list drama, duplicating technical work, etc will happen but hopefully this will contribute to having even more high quality open web implementations available.
[fn:0] http://www.chromium.org/blink/developer-faq#TOC-Is-this-goin...
If you're doing anything more complicated than serving static HTML and images to mobile devices you will already need to test on as many different devices as is feasible for you. It's basically unheard of for something to work across all WebKit based browsers just because your CI is telling you it works OK in desktop Chrome.
When it comes to Firefox OS it is more of a question of whether phone manufacturers will allow you to switch OS on your device or not, something that eg. FairPhone has been said to be investigating, wanting to ship their device with an option of either Android or Firefox OS.
But as long as Firefox OS' API:s gets standardized and implemented by others Firefox OS can't ever turn into an IE6 because there is nothing in Firefox OS that keeps you from switching to something else, which the apps in iOS do.
My phone is running Android 4.1.1 and the default browser is good, but my preference is for mobile Firefox 20.0, which I use instead. I'm glad my mobile accepts multiple browsers, because it allows me to choose the application I want to use.
What if iOS or WP8 had Android's market share? Do you really think that would be good for the web? We just happen to be lucky to have Android, an OS that does allow other browser engines on it, to dominate right now.
It doesn't even matter who will be the leader - if Apple leads, Android users will lose; if Google leads, Apple users will lose. Except if people start to buy smartphones based on the HTML rendering engine.
So there's a tradeoff--you're splitting people's efforts, and that's bad, but you're also removing pain points that slow down development.
Chrome definitely doesn't have any level of domination over the enterprise market like IE6 on Windows did. That was the problem with IE6 not the browser per se - it was revolutionary when it was released, MS just killed the team. The chance that enterprises will stick with Chrome is very unlikely.
As it stands at the moment, the only downside is the duplicated development between the Safari and Chrome teams. Webkit will suffer, but the web won't. Apple don't care enough, the web isn't the top of their priority list.
If anything, the iOS monopoly of mobile web traffic (in the first world) is a problem which certainly isn't changed by this fork.
That's my two pennies worth.