There should really be just one rendering engine. Dare to dream..
There should really be just one rendering engine. Dare to dream..
The overwhelming dominance of a single browser caused big problems on its own. We need healthy competition in this technology marketplace.
Right now they control Trident as they like. A shift to WebKit would mean ceding a lot of that control to Apple and Google and all the other WebKit contributors/maintainers.
> There should really be just one rendering engine.
No. That's really a terrible idea, because different rendering engine consumers have different priorities.
Luckily, even "webkit" has a number of forks that are somewhat incompatible for precisely that reason. So we're in no danger of this "one rendering engine" thing.
(A note: while we've already been close to having one rendering engine with a priority of "change nothing", having one with pretty much any other priority set is no better; those priorities will be wrong for _some_ consumer.)
competition is good
Users would still have a choice of browsers, but the web would be a much better place for users, and developers/designers.
Is it a good thing for designers for those bugs to be enshrined as a de-facto standard? I don't think so. The fact that other UAs don't have them might serve as pressure on webkit to fix them too. Maybe.