4 ms·
The issue is that the dominant engine developer uses their market position to push their competitors out of the market or to define their own web standards. The
by II2II 4y ago
The issue is that the dominant engine developer uses their market position to push their competitors out of the market or to define their own web standards. The former is what happened with IE in the late 1990's. The latter is what is happening with the Blink and V8 engines today.
As for 100% compatibility, most people will regard unexpected results as bugs or hindrances then switch to a compatible browser. You may be willing to deal with those incompatibilities. I may be willing to deal with those incompatibilities. Both of us are in the minority. Even technophiles who normally like playing with technology seem to stick to browsers based upon Chrome's engines (at least when given a choice) simply because too much of their life depends upon the browser.
- tgv 4y agoIf Apple were forced to allow Chrome on iOS, Chrome's influence would grow even stronger. So why do you think that's an argument against wrappers around Safari?
- Matl 4y agoBecause Safari's not up to snuff and also because Firefox should also be able to compete. If you block browsers based on Chrome's dominance, Chrome effectively already won. What I predict would happen is that Apple starts investing heavily in WebKit to compete and Firefox would have a compelling offering there like it does on Android. Most people would stick with Safari because is is the default and they wouldn't even mostly be aware that it now may be worth switching due to say uBlock Origin. Safari would continue to serve them just fine.
- Jcowell 4y agoIf there’s one thing I’m certain of is that given the ability to use it’s own engine Firefox will still lose to Chrome. Willing to bet $100.