Investigating the Performance of Firefox 4 and IE9
theweatherelectric writes "Mozilla's Robert O'Callahan has investigated the performance differences between Firefox 4 and IE9. He writes, 'As I explained in my last post, Microsoft's PR about "full hardware acceleration" is a myth. But it's true that some graphics benchmarks consistently report better scores for IE9 than for Firefox, so over the last few days I've been looking into that. Below I'll explain the details [of] what I've found about various commonly-cited benchmarks, but the summary is that the performance differences are explained by relatively small bugs in Firefox, bugs in IE9, and bugs in the benchmarks, not due to any major architectural issues in Firefox (as Microsoft would have you believe).'"
the summary is that the performance differences are explained by relatively small bugs in Firefox, bugs in IE9, and bugs in the benchmarks, not due to any major architectural issues in Firefox (as Microsoft would have you believe).
So MS is spouting some anti Firefox FUD? When did this start? How are we supposed to measure browsers against each other if one (or both) sides aren't telling the truth. My confidence is crushed ... just crushed.
I'm liking FF4 so far. I was using Chrome but they never fixed my endless "Sending request" bug, no matter how many times I and others reported it, so I'm giving up on them for now.
Occasionally living proof of the Ballmer peak.
Ultimate browser benchmark: Logging in, and posting on slashdot.
Funny enough, Firefox' "broken" fonts are thanks to using the same DirectWrite that IE9 uses. However, MS disables DWrite for fonts and uses GDI instead when running sites in compatibility mode. When running in standards mode, IE9 and Firefox have identical font rendering (there's a big MozillaZine forum thread with screenshots if you're interested). Also, some recent MS hotfixes for DWrite have noticeably improved font rendering. Have you used a recent beta with an updated system? But in the end, if you're not happy with the font rendering, you can always disable the hardware acceleration through the options.
What's stupid is the wrong stuff is being concentrated on.
If google maps loads in 3 or 4 seconds doesn't matter to me. What I want is for the whole browser not to hang its UI anytime one website is doing stuff. I hate opening tabs in the background and having the browser be unusable until they load.
And this is on a quad core i7, 8gb of ram.
It's easier to fight for one's principles than to live up to them.