[Novalug] browser/network responsiveness -- Safari uses KHTML
Bryan J Smith
b.j.smith at ieee.org
Sat Oct 3 11:18:47 EDT 2009
On Fri, 2009-10-02 at 15:56 -0400, Ken Kauffman wrote:
> In work from days gone by... the Mozilla engine used to wait for all
> artifacts to load before it would render. IE, however, would start
> rendering as soon as it received "enough" data to do so. Then it
> would continue to tweak the page rendering as new stuff rendered.
> Perhaps Safari works similarly to IE.
Safari is based on the KHTML engine, from Konqueror.
MS IE does a lot of stupid things, and is Win32-only (for those of us
who ever tried to support the Mac, let alone Solaris, versions). There
are things tied directly into the NT kernel and core DLLs, and it's been
that way since the mid-'90s.
It's also why when you disable things in MS IE, you don't really. Many
even when you disable both, you don't disable some functions. Why?
Because they are necessary for various Windows automation, especially
for Explorer and MS Office, like Outlook [Express]. ;)
> If you have access to a Windows PC, load Safari for Windows and do
> comparison tests on the same platform with Firefox.
Google's browser is having the same issues.
It's hard for me to trust anything but the Gecko engine, although I
won't talk negative about KHTML like I do MS IE.
Bryan J Smith Professional, Technical Annoyance
Linked Profile: http://www.linkedin.com/in/bjsmith
Only engineers can solve the growing needs of consumers
Stop being "aware" (that's so '70s) and start supporting
real solutions that actually work and sustain the planet
More information about the Novalug