3 ms·
Can I question the orthodoxy on this one? Suppose WebKit or Blink are the one engine that everyone uses. Do you know how much uncertainty and effort that will
by EGreg 8y ago
Can I question the orthodoxy on this one?
Suppose WebKit or Blink are the one engine that everyone uses. Do you know how much uncertainty and effort that will save around the world that goes into browser compatibility and quirks? Look at the x86 architecture or POSIX as well.
Here is my serious practical question: this is open source, so if you want to make some extension, you should be able to distribute it. And if it becomes so popular as to be merged into the core, or included with the main distribution, then it will be.
It seems on balance, this would be a good thing.
- sdwisely 8y agoit's more complicated than that though. Nobody is lamenting the loss of the edge engine. Things like choice of video codec, drm module, etc have shown is it's a good thing to have a few different vendors with a seat at the table for standards. Most important of those is Firefox.
- ben-schaaf 8y agox86 and POSIX are actually great comparisons to the current state of browsers. They all have well defined standards that everyone should follow in theory. In practice CPUs have bugs[0] that kernels and applications make a lot of effort to work around. There are also enough implementation/non-compliance quirks in POSIX[1][2] implementations to matter when porting. Just like all of the web standards, x86 and POSIX don't solve the compatibility problems that come from innovation. [0] https://wiki.osdev.org/CPU_Bugs https://wiki.osdev.org/CPU_Bugs [1] https://personal.opengroup.org/~ajosey/tr28-07-2003.txt https://personal.opengroup.org/~ajosey/tr28-07-2003.txt [2] https://en.wikipedia.org/wiki/Linux_Standard_Base https://en.wikipedia.org/wiki/Linux_Standard_Base