Quote
leveck
There is no way that IE7 could give such bad results compared to the others... I dont use it but it certainly isnt that much worse than FF or Safari... Sounds like a Google Chrome fanboy to me.
I mostly agree, but: IE7 does give bad results.
IEs' 5.5-7 are even slower than e.g. IE 5.01 and 8.
IE6 & 7 are the most resource hungry and slowest browsers - if compared with current and past IE browsers ( at its times IE 6/7 were only ok, if You did not compare with K-Meleons, Operas, Firefoxes, Safaris or even IE 5.01 and 8
).
"Sounds like fan..." - IMHO Google Chrome is fast but loosing much time on spying -
Iron is AFAIK todays state of the art browser - for PPL that want the khtml engine. No frills (extra gadgets) or redundant spyware items. Safari 3 is using an older khtml implememntation with a slower JS engine (Safari 4 will use the new JS-engine like Iron).
As for Firefox3.x GRE & its much venerated new JavaScriptEngine?
IMHO its GRE & JS engine is the state of the art. AFAIK it is the fastest JS-engine & just that after only a few months of specialists' optimisations!
However it is likely that K-Meleon will be fastest with that too.
Comment: Fast JS is needed for many new web applications & compared with Firefox and other future Xulrunner apps K-Meleon.exes just look good.
(
K-Meleons higher speed is by design. Firefox etc. use the whole big Xulrunner GRE (includes files for mail etc.) - while K-Meleon uses & loads only the browser components of it = less code = more speed ( one up for k-meleon
).
The test results with Chrome, Hao's betas and Dorian's pre-versions for best JS implememntation & GRE were published in this forum.
p.s. On Win32 IMHO Gecko runtime environment is state of the art.
IMHO On Win32 K-Meleon is better by design than every other Gecko browser
K-Meleon project has only one problem - too few devs - so K-Meleon 1.6 will be late
Edited 1 time(s). Last edit at 11/25/2008 01:27AM by guenter.