4 ms·
When Apple announced that they were going to use KHTML in Safari (when they announced Safari) they stated that it was due to the library's small footprint. I as
by pyre 16y ago
When Apple announced that they were going to use KHTML in Safari (when they announced Safari) they stated that it was due to the library's small footprint. I assume that they didn't want to spend the time to reign in the Gecko engine to do what they wanted it to do (or hack/optimize it down to size).
Just because something exists and seems to be 'good enough' doesn't necessarily mean that it would be a good fit. Unless you develop for WebKit, Safari, Firefox and/or Gecko, I'm not sure any of us are really qualified to make those kinds of statements. Also remember that you can't compare the current state of the two codebases. You have to compare the state of the codebases at the time that Apple created Safari/WebKit.
- wdewind 16y agoAgree to disagree, but I hope you don't complain about browser fragmentation.