Having a single rendering technology to support would be preferential but it's direction can't be controlled by just Google.
Of course this would then mean the end of the Foundation and Mitchell Baker's $3m per year so will never happen.
Having a single rendering technology to support would be preferential but it's direction can't be controlled by just Google.
Of course this would then mean the end of the Foundation and Mitchell Baker's $3m per year so will never happen.
Really? I prefer there are a few, but mostly compatible techs in that space. This is the VM that runs almost all desktop (client) software these days. Having only one implementation would IMHO be a disaster.
End users of browsers do not have this insight into their tools.
Yes, Oracle's JVM is dominant (but not on Android, which is a huge installed base). So is Chrome in browser land. Still good that Java has many, and FF exists.
[1]: https://en.wikipedia.org/wiki/List_of_Java_virtual_machines
But a lot of us still pucker up if you mention the word "IE6" and we never want to risk going down that path again. :)
There's a balance between diversity and monopoly that can be struck.
In my opinion if there is only chromium left it is the sign that http/html/css/js needs to be replace with something new that would allow healthy competition without being funded by a multi billion company
I disagree. Monocultures never work out well for users.