5 ms·
You could make exactly the same argument about Webkit itself, or about any of the extant HTML engines, could you not? Why did any of them decide to complicate t
by Lagged2Death 15y ago
You could make exactly the same argument about Webkit itself, or about any of the extant HTML engines, could you not? Why did any of them decide to complicate the web by multiplying the number of engine-specific bugs in the wild? Why didn't every browser project just start with the Trident engine in IE?
- eridius 15y agoNot that I disagree with your point, but Webkit wasn't a new rendering engine. It was a fork of KHTML (the engine behind Konqueror).
- seabee 15y agoOnly MS can improve and fix the Trident engine, for a start.
- Lagged2Death 15y agoYes, which is an advantage, if you're of the opinion that the existence of a variety of engines (and the corresponding existence of a variety of bugs) is a hassle that's hurting the web. That's not my opinion, mind you.
- deleted 15y ago[deleted]