Comments on: Firefox, Google's Chrome speed past IE, Opera
Mozilla's Firefox and Google's Chrome, plus the WebKit developer project included in Chrome and Safari, are dramatically faster than proprietary browsers, according to recent tests.
Mozilla's Firefox and Google's Chrome, plus the WebKit developer project included in Chrome and Safari, are dramatically faster than proprietary browsers, according to recent tests.
There were plenty of e-book readers on display at CES 2010, but many question whether the market for such dedicated devices can support all the new entrants.
Photos: E-readers at CES 2010
Vintage computer historians have long revered the Altair 8800. As it turns out, an unknown computer project at Sacramento State beat the Altair by three years.
Images: The first microcomputers
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to the Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is general manager of the Americas division and vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.
Add this feed to your online news reader
I agree WebKit has a fast JS engine but to run a WebKit test against it and others and claim it's the fastest isn't much of a victory.
With Tracemonkey, it feels faster than Chrome.
If I recall correctly, one of the problems with these sorts of benchmarks is that they only test a narrow aspect of what it takes to render content. For example, if the javascript engine in browser A gets a javascript task done 50 ms faster than browser B, but browser B renders/displays the result of that script 150ms faster, then the user experience will be faster on browser B.
I am so damn tired of these crotch-grabbing, narrowly-focused benchmark-fests that masquerade as "news" to tech journalists - particularly when they aren't even testing shipping code. Please find something more substantive to write about.
Like: http://www.jsballs.com/benchmark.html
And personally DOM manipulation is a much better test of how fast the javascript engine will feel to users since DOM manipulation is common practice on all AJAX sites.
Browsers are free, nobody really wins or loses and it's completely asinine for any one person here to be concerned about which browser everyone else is using. Use whatever browser you want but the content on the webpage you are viewing is still the same.
It is asinine to state that because all browsers deliver the same webpage, the speed with which those pages are rendered is unimportant. Unless you had your head buried in the sand for the last couple years, you'd realize that vast swaths of delivered Web pages are "dynamic" in nature these days - they're no longer static content. Javascript speed (as well as applet speed, flash speed, etc.) matter! It is easy to see the difference between IE and Firefox 3.1 (or Chrome) on such web pages - so the difference isn't just some academic milliseconds. Try them! Check out things like Google Docs (or even just "iGoogle" is perceptibly faster under Chrome/Firefox than it is under IE8).
I agree with you all the way. Information should be out there for people to see and to make better choices.
of course milliseconds are not the prime factor here, they are barely noticeable, but like i said, we need to know.
Because when you push to the limit, every advancement is a milistone, if we didnt care, science would not exist.
I consider this a very legitimate test, and also consider you (viper396) someone who should hate less and embrace more.
My guess is that Microsoft will get sick and tired of every company and their brother using goverment intervention to dictate business to them and finally remove most of the rest of it in Windows 8 moving forward. Internet Explorer, Media Player, and anything else that is not required to run the system.
Live Services will then host a wealth of integrated software plus services through Azure and Mesh so it won't matter if they are included or not. You will still want to use the OS that creates all the pieces for a polished fit and finish experience. For those that aren't interested in that, there is everything else.
Ok, I'm ready, break out the clubs, knives, guns, granades, and lazers to shred me to pieces- it's ok, I'm already cloked, shields up, and light years away!
So I have a basis for access speed for all four. IE is the slowest for anything. The other three are very
close, but ..... Chrome is slowed down by the doubleclik accesses and all the similar things so much,
that it's basic speed is negated. Firefox not so much so a little faster. Opera, not at all, so is the fastest
of the four. At least on my PC(s), all four. I also have Maxthon2, which appears to be an IE lookalike,
but is about as fast as Firefox. I only use Maxthon2 to access Hotmail on the internet.
Betas and nightly builds are a good thing to test, because then there is a record of progress being kept.
Without doing such a thing, people probably wouldn't even care to advance stuff.
Benchmarks are good for everyone.
I just hope Opera and Microsoft spend more time getting JavaScript up to speed.
I suggest they go look into V8 and learn something, Google sure encouraged others to do so.
It is just a shell around IE to try and hide the fact that it is a turd.
Basically, it was a test to see how fast the browsers would render a 32x22 grid of tiles 25 pixels squared with a grass HTML "texture".
The grass was made of divs with 1px widths, random position and heights.
The method of drawing them all was using the innerHTML property of a parent div. (drew them all separate, rather than store in variable and draw them all at once)
Ran the test across several browsers, all failed pretty badly in time, some going on past a minute. (some hung..)
I lowered the density to 1 bit of grass per tile, better speeds, but not quick enough for web use, needs to be quicker, 15+ seconds isn't acceptable anymore.
I lowered it even more to only draw the divs on every 7th tile, Firefox 2 done it within half a second, Chrome within around 3 seconds, not sure what IE7s time was again.
I decided to add in a little man that will move up automatically, then wrap to the bottom when it reaches the top, moved fairly fast across them all.
I replaced all the HTML textures with images instead... strange thing now is Firefox 2 is the slowest with the man test, AND it was using incredibly high CPU to do it, whereas every other browser tested (Chrome, IE7, IE8, Safari, Konqueror,Opera 10) was barely hitting the 5% mark (dual-core 1.6GHz)
Never tried Firefox 3 because Mozilla seriously annoyed me with the stupid SSL thing, don't even want to install it anymore...
It was a pretty interesting test, i should do a better test with actual times some day, and test the other browsers with the HTML "textures".
Mainly researching it for AJAX-based animation.
This site has some interesting projects on that actually, found it the other day there http://osflash.org/ajaxanimator
- by kudos2uguys January 28, 2009 5:06 PM PST
- I'm testing IE8 and can I say it's not slow......it's S L O W. I also have Firefox and Chrome. Chrome is now my default because of the speed... There are some small bugs here and there in Chrome and I'm using the latest Firefox 3 beta client and it's still not as fast as Chrome. Leave it to Microsoft to bring out something as slow as IE 8 and think that it's an improvement, what's wrong with those people?
- Like this Reply to this comment
-
-
- by MSSlayer January 29, 2009 3:37 PM PST
- Chrome may be fast, but it is also spyware.
- Like this
-
Showing 1 of 2 pages (37 Comments)