Slashdot Log In
FireFox 3.1 Leaves IE in the Dust
Posted by
CmdrTaco
on Mon Oct 20, 2008 10:00 AM
from the i-just-want-fewer-beachballs dept.
from the i-just-want-fewer-beachballs dept.
Anonymous writes "Granted, FireFox 3.1 is just a beta and IE 8 is also in beta, but it looks like Microsoft has some ground to make up when it comes to browser performance. Given that Mozilla appears to be on a much faster cycle than Microsoft with this stuff, it's also possible that it could increase the gap even more before IE 8 is GA, no?"
Related Stories
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
And yet (Score:4, Insightful)
Re:And yet (Score:5, Funny)
Their speeds all suck next to lynx!
Parent
Re:And yet (Score:5, Funny)
Re:And yet (Score:0, Redundant)
Their speeds all suck next to lynx!
Bah! you damn moderators can't accept the truth!
Parent
Re:And yet (Score:5, Funny)
(actually, modding redundant implies that they had already accepted it)
Parent
Re:And yet (Score:5, Funny)
Parent
Re:And yet (Score:5, Funny)
Pshaw! Youngster. Your UID barely fits inside 16 bits. In _my_ day we had to whistle the 1's and 0's through an acoustic coupler!
Parent
Re:And yet (Score:5, Informative)
Well, javascript-wise, maybe not. I've spent the last week doing some extensive testing on pure javascript performance (not DOM-tree manipulation, etc) using a little raytracer [googlepages.com] I hacked up overnight.
Opera is noticably above average, in this respect. More importantly, however, you might note that the Firefoxes are absolutely, hideously bad at memory management. When rendering a big scene here, Safari will do it in a fraction of the time using 60mb of RAM, whereas Firefox 3.1beta's memory usage spirals out of control and into swap space. And the JIT compiler is way broken still :)
Anyway, here are some figures (only meaningful when comparing different browsers on the same box):
IE 7.0.5730.13 -- 10.1 seconds
Firefox 2.0.0.17 -- 9.9 seconds
Safari (win32) 3.1.1 -- 5.9 seconds
Opera 9.60 -- 3.6 seconds
Firefox 3.1b2pre (no JIT) -- 2.8 seconds
Safari (win32) 2008-10-15 -- 1.0 seconds
Google Chrome 0.2.149.30 -- 0.8 seconds
Firefox 3.1b2pre (JIT) -- anywhere between 0.6-35.0 seconds
Parent
Re:And yet (Score:5, Funny)
When rendering a big scene here, Safari will do it in a fraction of the time using 60mb of RAM, whereas Firefox 3.1beta's memory usage spirals out of control and into swap space.
Wow, 60 milli-bits of RAM, that's more than amazing!
Parent
Re:And yet (Score:5, Funny)
Yes but I have 1.21 jiggawhats of CPU
Parent
Re:And yet (Score:5, Interesting)
Thanks, heh! For a minute I thought I had an original idea but it turns out there other other (better but slower) js raytracers out there. Humm :)
Webkit is great. If you're running that you might actually see some animation here [googlepages.com] (10fps+ in Safari nightly here). I wonder if the demoscene guys are insane enough to write demos for browsers?
Parent
Re:And yet (Score:5, Informative)
Actually, you're wrong -- Firefox 3.1 comprehensively outperforms Opera in pretty much all tests now.
On the other hand, what does blow the FF 3.1 beta out of the water, are the latest WebKit betas. Here's the stats on my machine:
Sunspider (faster times are better)
FF3.0.3 - 2697.2ms
FF3.1 - 2442.8ms
WebKit - 702.6ms
V8 Benchmark (more runs are better)
FF3.0.3 - 199 runs
FF3.1 - 241 runs
WebKit - 2087 runs
ACID 3
FF3.0.3 - 71 and significant laggyness
FF3.1 - 89 and significant laggyness
WebKit - 100 and passes timing tests
Parent
Simple Really (Score:4, Insightful)
This destroys Microsoft's claim that their intimate knowledge of the OS that runs IE will increase performance.
This proves that Microsoft's intimate knowledge of their OS actually inhibits performance of IE and therefore all other Microsoft products.
Microsoft is a victim of their own feature-rich corporate culture. They are a victim of their customers non-uniform demands.
The issue is similar to the ones that have always plagued Java; you have to load massive libraries to do miniscule tasks and that causes noticeable overhead, when they were sadly intended to save time! Firefox is simply more minimal, and it is through their actively sought after security footprint that they deliver better performance by default.
Firefox loads what you need to surf and also lets you modify the experience -- you are in control.
Add with that experience, superior plugins like NoScript, and you also save bandwidth because Flash files don't load by default and scripts don't tie up resources unless you approve them to do so. NoScript was designed for security, but with the added benefit that you get faster performance with it.
Even when you look at Google Chrome, which is also a valid attempt at increasing performance (they flaunt security as a pillar of their design, but their cheerleading is unwarranted), the fact that you can't control scripts that are allowed to run, limits the user and make the user bound to the control of the webmaster, who typically controlled by a business or corporation that is only in it for the money and will infringe on rights of users without any form of conscience or compassion.
Re:Simple Really (Score:4, Insightful)
This destroys Microsoft's claim that their intimate knowledge of the OS that runs IE will increase performance.
To be precise (by pulling numbers out of my ass), if IE had 50% of Firefox's performance to begin with, and embedding into the OS gave it a 50% advantage, it'd still only have 75% of Firefox's performance. But MS's claim could in theory still be true.
Of course, given their all-around incompetence it's probably not true.
As for Google Chrome, it makes perfect sense to bind the user to the webmaster's control. After all, for many important things like e-mail, calendaring, and many more, that webmaster is probably Google. (After all, how many yahoo.com or live.com users would install a Google browser?) And Google loves it when you can't block their cookies or stop them from doing whatever they want to spy on you.
Parent
Re:Simple Really (Score:5, Funny)
This can't be true because Google said they would do no evil. Unless OH SH-
Parent
Re:Simple Really (Score:5, Insightful)
Hmm, I must have been teleported to some alternate reality where IE actually has more features than Firefox. The way I see it, even the barebones FF install has more than standard IE. One glance at about:config would confirm that.
Parent
Re:Simple Really (Score:5, Interesting)
This destroys Microsoft's claim that their intimate knowledge of the OS that runs IE will increase performance.
Really? Where was this claimed?
This proves that Microsoft's intimate knowledge of their OS actually inhibits performance of IE and therefore all other Microsoft products.
That's quite the leap there. Where's your evidence to bridge those thoughts?
The issue is similar to the ones that have always plagued Java; you have to load massive libraries to do miniscule tasks and that causes noticeable overhead, when they were sadly intended to save time! Firefox is simply more minimal, and it is through their actively sought after security footprint that they deliver better performance by default.
I don't think anyone said using libraries increased performance. What it does do is allow you to build an application faster, because you don't need to re-invent the wheel. You're also acting like speed is the only important factor here. I've been using IE8 beta more because of the built in developer tools, and being able to switch between IE8 standards mode and IE7 mode... which means I don't have to check FF's rendering as much. Besides, IE8 is so fast, that it hardly seems worth if it FF is faster.. either will be great for browsing, because both are now really really fast. It's not like the ridiculously slow IE7.
Add with that experience, superior plugins like NoScript, and you also save bandwidth because Flash files don't load by default and scripts don't tie up resources unless you approve them to do so. NoScript was designed for security, but with the added benefit that you get faster performance with it.
Performance is not the end-all be-all of browsing. I'm sure someone so included could whip up an add-in like NoScript in IE as well.
Even when you look at Google Chrome, which is also a valid attempt at increasing performance (they flaunt security as a pillar of their design, but their cheerleading is unwarranted), the fact that you can't control scripts that are allowed to run, limits the user and make the user bound to the control of the webmaster, who typically controlled by a business or corporation that is only in it for the money and will infringe on rights of users without any form of conscience or compassion.
I'm not sure most users care as much as you about controling scripts. For example, I'm looking forward to see what features FF comes up with, because I think there are other new features in IE8 that look pretty compelling, like WebSlices and Extenders.
Parent
Re:Simple Really (Score:5, Insightful)
Even when you look at Google Chrome, [snip] the fact that you can't control scripts that are allowed to run, limits the user and make the user bound to the control of the webmaster, who typically controlled by a business or corporation that is only in it for the money and will infringe on rights of users without any form of conscience or compassion.
Is it surprising that a company that makes it's money from advertising would want to make it difficult for users to block adverts? I think not.
Parent
Re:Simple Really (Score:5, Insightful)
Remember those anti-trust cases with the Win95/98 and IE bundling? Yeah, around that time.
No, I don't remember performance being mentioned in the anti-trust cases. And why would they? It would highlight an uncompetitive advantage and weaken their position.
Citation needed.
Parent
Re:Simple Really (Score:4, Funny)
They did say that IE was a basic building block of their product and that removing it would slow everything down and would make it suck.
Imagine... a windows OS that sucks.
Mind thrashing, ey?
Parent
Re:Simple Really (Score:5, Interesting)
Microsoft did tout the benefits of integrating IE into the operating system including reduced memory usage and increased functionality (for the OS as well as third parties). See this artcile [harvard.edu] for a summary of testimony and cross examination of Glenn Weadock.
The appeals court said [nytimes.com]:
Parent
Re:Simple Really (Score:5, Informative)
No, I don't remember performance being mentioned in the anti-trust cases. And why would they? It would highlight an uncompetitive advantage and weaken their position.
Citation needed.
Well if you're willing to take Wikipedia [wikipedia.org] as a citation, then:
"A number of videotapes were submitted as evidence by Microsoft during the trial, including one that demonstrated that removing Internet Explorer from Microsoft Windows caused slowdowns and malfunctions in Windows." (Emphasis added)
Microsoft later withdrew the claim, but only because the plaintiffs spotted that Microsoft attempted to mislead the court with their initial video demonstration. I'm still disgusted that no one from Microsoft was directly prosecuted for any of that.
Parent
Re:Simple Really (Score:4, Informative)
Because in most programming libraries, time is normally expressed in milliseconds.
Parent
Benchmarks were versus IE7 ... (Score:5, Insightful)
Having said that, the speed improvements are very impressive, in what ChannelWeb says and other reports. And yea, FF3.1 is setting a darn high bar for IE8 - bring it on FF!
Re:Benchmarks were versus IE7 ... (Score:5, Funny)
Don't worry, I'm sure we'll still get a bunch of uninformed posts from people who didn't read the article, talking about how they're not surprised Firefox 3.1 outperforms IE8 when IE8 wasn't benchmarked.
Parent
Tired of Perma-Beta (Score:4, Interesting)
Re:Tired of Perma-Beta (Score:4, Informative)
Huh? Firefox 3 is in production. Firefox 3.1 is in beta. As in real beta, not out yet, in testing.
Parent
Java != Javascript (Score:5, Insightful)
When is the press going to realize that Java != Javascript? (Or Java !== Javascript, even!) Comparing "Java" performance between browsers is meaningless. (And isn't what SunSpider does anyway.) Comparing JavaScript performance has a very real impact on the users.
Re:Java != Javascript (Score:4, Insightful)
When is the press going to realize that Java != Javascript? (Or Java !== Javascript, even!) Comparing "Java" performance between browsers is meaningless. (And isn't what SunSpider does anyway.) Comparing JavaScript performance has a very real impact on the users.
I was surprised about that too. Mozilla was working on a faster javascript engine, and suddenly it's their Java performance (which comes from the JVM, right?) that blows IE out of the water.
Looks like the summary is as bad as the article it tries to summarise.
Parent
Re:Java != Javascript (Score:5, Interesting)
When is the press going to realize that Java != Javascript? (Or Java !== Javascript, even!)
Heh heh heh. Believe it or not, when I first interviewed for a Senior Editor position at Web Techniques magazine, back around 2000, I had never been any kind of Junior Editor before. I just assumed I could do the job. In the course of several interviews, the editorial staff asked me a number of questions about Web technologies, including one from the editor-in-chief: "What's the relationship between Java and JavaScript?"
I got really nervous for a second. I wasn't sure what to say. My interviewer raised an eyebrow. Finally I stammered out, "Well... I'm not sure I really know how to answer that. The truth is there really isn't much of a relationship." I then talked about Sun's release of Java 1.0, and how Netscape had been working on a language called LiveScript that they planned to include in their browser, and that they changed the name to JavaScript as a favor to Sun. But, I emphasized, the languages were really not very closely related, and I felt a little awkward comparing them without maybe a more specific question. My interviewer jotted down a couple of notes and suggested we move on to another topic.
I later found out that a big part of the reason they hired me, despite my lack of publishing experience at the time, was because of all the candidates they interviewed -- some with years of experience in the trade press -- not one but me had a satisfactory answer to the Java/JavaScript question. Most said something along the lines of "JavaScript is a stripped-down version of Java for Web browsers."
So in answer to your question -- when will the press get a clue -- I'm not sure. But I can testify from firsthand experience that they're working on it! ;-)
Parent
Re:Java != Javascript (Score:4, Informative)
In JS, it's "not identical". It means "don't try to do any implicit casting - not only must their values be the same, but their type must be the same too"
I get pinged on it all the time when I'm running other people's JS through http://www.jslint.com/ [jslint.com]
Parent
What's "GA"? (Score:5, Funny)
Is "GA" a common abbreviation? I assume it's a contraction of "generally available", but I did think of, and discount, a few other possibilities first given it's used in conjunction with IE8;
God Awful (too obvious)
Grizzly Adams (not sure where the bad 80s drama comes into things)
Ground to Air (IE could be a Weapon Of Markup Destruction..)
Goatse Arse (Ass if you're American)
Gabon (.ga is the country code for there..)
Standards Non-compliant (using Microsoft Alphabet)
Re:What's "GA"? (Score:5, Funny)
When Microsoft releases a product it goes from CTP (Community Technology preview) to RTM (Release to Manufactuing) to GA (Genuinely Assinine).
Parent
Georgia (Score:5, Funny)
I think it's Georgia. Internally Microsoft doesn't use terms like "alpha" and "beta": a product starts in "Florida" and moves closer to Redmond, so "Washington" means "bug-free". When it reaches "Georgia", it's ready to ship.
Parent
Re:What's "GA"? (Score:4, Funny)
Parent
Does this really matter? (Score:4, Insightful)
Re:Does this really matter? (Score:5, Insightful)
I don't know about that. I switched to, and am still using, Chrome since it seems much faster. For many people, all they use their computer for is the web browser, so a faster browser could be significant.
Parent
Re:Does this really matter? (Score:5, Insightful)
There are people who will use 1 browser because it is "the internet".
there are people who will use 1 browser because it is God's only browser and there is only one.
There are people who will use 1 browser because they cant be bothered to change.
And then there are people who will want to latest, fastest, feature-rich, talked-about browser. And if FF gets "superfast" stickers all over it in the popular press and blogs, people will want to use it. Nobody really wants to be stuck with yesterday's slow old slowness, not in the Internet Age. We've all been conditioned to always go for the upgrade, give us any reason and very many of us will.
Parent
Poor Summary (Score:4, Insightful)
this is not news (Score:5, Informative)
If you've even remotely been keeping up with FireFox, WebKit and IE progress, it's no surprise that IE8 fares poorly. It fared poorly the day it was released, which was about two months ago. Why are we getting this story now?
As a side note, IE8 does fix the pathologically bad performance IE6/IE7 exhibited on certain SunSpider benchmarks. That alone should improve its overall SunSpider score by an order of magnitude. Its javascript engine will still be 2-3X slower than FireFox and Safari, but it will at least be in the same "ball park".
Microsoft's foolish mistake (Score:5, Interesting)
For the life of me, I can't understand why Microsoft continues to abandon its strength.
It feels like the .NET koolaid is coming even to the IE team. Microsoft's .NET push now borders on maniacal, standardizing on .NET and in places where it should not be standardized. Performance matters, particularly when processors aren't getting any faster, just more parallel. Microsoft's has left C++ to languish, has all but abandoned C, and as such has no real performance tool in their own arsenal.
At the same time, the OSS community is actually slogging through and solving some of the difficult problems of making large projects in C++ that perform - getting better experience with the STL, when to use and when not to use, changing compilers to respond, developing automated testing methodologies to overcome what the compilers can't detect, and so on.
There should be no reason for the Windows desktop to be stagnant for fast applications, but Microsoft has basically abandoned it and is pushing developers to do the same. All the new display stuff in Windows requires .NET.. one wonders, how long will it be before Linux has similar systems but are presented as a simple C library that any system can use, regardless of whether it is a managed platform or not.
Re:Microsoft's foolish mistake (Score:4, Informative)
It feels like the .NET koolaid is coming even to the IE team. Microsoft's .NET push now borders on maniacal, standardizing on .NET and in places where it should not be standardized. Performance matters, particularly when processors aren't getting any faster, just more parallel. Microsoft's has left C++ to languish, has all but abandoned C, and as such has no real performance tool in their own arsenal.
But IE isn't built on .NET is it? And there are improvements in MSVC in VS2008 for both C and C++ and they've had OpenMP and a much improved STL for two versions now.
For my interest, when have major OSS projects "changed compilers" to respond? I can't think of any examples.
Parent
Fair tests? (Score:5, Insightful)
I don't see that the things they mention are fair or informative tests. Yes, there's some browser infrastructure involved but other components are doing most of the work:
Maybe Firefox 3.1 is much faster than IE 8 but this article doesn't tell me anything new.
What's so surprising? (Score:4, Informative)
It's not like IE has not been a slow dog in javascript performance and standards adoption. Yeah, IE 7/8 are supposed to be an improvement, but since IE is years behind and their development cycles seem to be as slow as their javascript engine (probably due to compatibility) it's not like IE 8 or 9 is going to catchup with the rest of the browsers easily.
BTW, those benchmarks in TFA were probably run with the new tracemonkey javascript engine disabled (it need to be enabled manually in about:config). And my firefox nightly version passes 93/100 on the acid 3 test.
Yes, but how about stability? (Score:5, Informative)
Um (Score:5, Insightful)
IE 8 is a major revision.
FF 3.1 is a minor revision.
Just about any version of Opera is faster than them both.
Learn to compare things.
Re:Um (Score:5, Informative)
Parent
SilverLight Test? (Score:5, Funny)
Where's the SilverLight test, huh? I bet IE wins that one..
Now, can they cut down the spam? (Score:5, Interesting)
I mean, OK, it's nice to have the name and URL both in the dropdown from the location bar, but do they have to use so much space doing it?
Camino had that months earlier, without burning nearly as much real estate on it.
VERY misleading summary! (Score:5, Insightful)
The summary mentions IE8 more than once, but the article is comparing Firefox 3.1 to IE 7 (yes SEVEN - you know, the OLD one!)
The Javascript engine in IE8 is much faster than the one in IE7, so it's a pretty unfair test in the first place and should never have been posted in the first place.
Many posters above already seem to be confused about the IE7/8 thing.
Irrelevant measures of performance (Score:4, Informative)
It is my understanding that the primary advantages of FF 3.1 are speedups to Javascript and adoption of new HTML tags.
For me (and for much of the web browsing community, such as my cousin, aunt & father, e.g. the 50-84 y.o community) these are USELESS.
1) I am slowly converting my family entirely over to using Firefox with NoScript -- because *anyone* who allows random internet sites to run software on their machine is *nuts* [1].
2) A significant majority of "common" sites will not be using enhanced HTML tags because they have to continue to work with the installed browser base.
This is another example of Mozilla developers getting side-tracked with respect to what is important to *them* rather than what might be important to the community [2].
1. The *real* advantage of Firefox is the selected enabling of Javascript for a few "trusted" relatively non-commercial sites (e.g. gmail, ones bank, ones broker) using NoScript. I will assume the display of pages from such sites is relatively unimpacted by Javascript speedups (since they tend to be network bandwidth or user input consrained). [Though it is worth noting that the gmail javascript appears to be becoming a bit of a pig.]
2. It is worth noting that my cousin, my aunt and my father continue to survive on the internet quite well using dial-up connections (in large part because they live in regions where DSL (or fiber) is unavailable and Cable is too expensive). I presume that G3 service will fall into the $$$ category even when reasonably priced modems that can connect their computers to the net become available.