Mozilla Rechallenges Google in Browser Speed Race

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
[citation][nom]GiveMeFF64[/nom]If only Mozilla would move into the 21st century with a 64 bit Windows version...[/citation]
waterfox, its what i use and i have yet to have a compatibility problem.
[citation][nom]danwat1234[/nom]Now only if firefox could use a CPU for each tab render like Chrome does[/citation]
hell no, chrome already crashed my computer when i open allot of tabs, if ff did that, it would be just as bad
 
Interestingly, the only time I have problems with FF nightly build is using googledocs? deliberate non compliance with standards? Oh and is there an Adblock + plugin for Chrome yet? Check the difference in load times for heavily add bound pages with adblock on and off.
 
[citation][nom]A Bad Day[/nom]I become somewhat worried if a problem also existed in version 15 and maybe even 14.And for your information, I gave Beta a try. The problem also exists.[/citation]
Why does it so often elude people to consider that if a program does not perform as expected, it might actually be caused by some other software, hardware or driver issue present in the PC?
Everyone has a unique computer and different browsers will fare differently in each unique environment. Which works best in my system may not work best for some other systems. We just need to try each one and choose for ourselves.
In the end though, browser performance is fast enough for all the big players that it is not the first thing I consider when making my choice anymore. Instead, I consider which browser offers the functionality and interface (including Add-ons/Plugins) that appeals to me and my needs.
 
[citation][nom]carnage9270[/nom]About as useful as a poopie-flavored lollipop. The browser wars were over long ago. I guess it's all about the nostalgia?[/citation]
The current browser war is just getting stronger. It's far from over.

[citation][nom]livebriand[/nom]I'd mainly like to see them work on making the UI faster - Firefox's benchmarks don't mean shit when the browser constantly freezes on my E350 machine. (Chrome is completely smooth, in comparison.)[/citation]
This. All the javascript speed in the world doesn't mean stuff all if it takes 1.5 seconds to switch tabs. 1.2 seconds to open the tools menu. 0.8 seconds to open a new tab. Even Chromium-based browsers can lag when it comes to these functions. I'm not 100% sure about the latest Opera version, but have any of you guys tried Opera 10.10? It's a couple of years old, but install it, give it a spin. Don't use it as your primary browser, but just notice how smooth everything is. It truly gives you the impression that it is a fast browser, because everything to do with the UI is absolutely instantaneous.

[citation][nom]A Bad Day[/nom]For some reason, it keeps giving me "Luna error" and AVG is marking it as a virus...[/citation]
AVG sucks, I hope you realize that.

[citation][nom]RogueKitsune[/nom]Contains i686 and x86_x64 builds of firefox:http://ftp.mozilla.org/pub/mozilla [...] tral-l10n/Also with the exception of silverlight every other plug-in works fine out of the box for the 64-bit version. Silverlight requires a little more effort to get it working properly.[/citation]
Silverlight is redundant. Microsoft even gave up on it.

[citation][nom]alidan[/nom]hell no, chrome already crashed my computer when i open allot of tabs, if ff did that, it would be just as bad[/citation]
That's why Firefox needs to give its users an option to enable or disable tab sandboxing. Disabled, it would run as a single process. Enabled, it would (should) run better on multi-core CPU's and systems with larger memory.

I tried switching back to another tab in Firefox while a tab was loading, and it refused to switch to the other tab until the loading tab had initialized loading (got a response from the target website). This meant that for roughly 4 seconds, the entire browser was effectively 'frozen'. (Aurora 15.0a2) Strangely enough you don't see this 'freezing' in Opera, despite it also being a single-process browser.

[citation][nom]cookoy[/nom]i use FF and Chrome regularly, but can't reach Opera website for past couple of months.[/citation]
Cannot duplicate this problem. I can reach Opera's website just fine in any browser. Check your hosts file and any content blocking software or addons you may have.
 
really!!! 32 bit?....are we going backwards?....am i missing something?....the developers need stop being lazy and work harder on making their websites behave properly on 64bit browsers....for now 64bit browsing is mediocre at best
 
[citation][nom]A Bad Day[/nom]Then, someone on the client side has the bright idea of pointing out that it's broken in IE8, IE7, and especially IE6.[/citation]

EVERY browser has inconsistencies. Also IE6 is way up there of course.
 
[citation][nom]Anonymous[/nom]If only Mozilla would move into the 21st century with a 64 bit Windows version...[/citation]
You could move into the 21st century with Linux, where we do have 64-bit Firefox....
 
[citation][nom]freggo[/nom]As a web developer I'd love to see an improvement in page layout consistency.It is frustrating to look at a webpage, even a fairly basic one, in 3 different browsers and see it rendered differently; then having to explain the difference to the client :-([/citation]

Sigh... that's the whole POINT of HTML as originally conceived. HTML is supposed to describe a page, and then the browser/user is supposed to decide how best to display that content given the display hardware. You should be able to see the same content on a high-end workstation PC or a text-only VAX terminal (my first web browsing experience) but there's no guarantee it's going to look the same way, only the best way. And users are supposed to be able to be the final arbiter in page display. If a page looks completely the same everywhere, then HTML is being over-ridden. Page layout ultimately should be decided on the receiving end.
 
Status
Not open for further replies.