G4 optimized Firefox

Does it make a noticeable difference though? I think the big difference will come when they stop using QuickDraw and use Quartz instead for rendering.
 
cfleck said:
isn't this just a matter of compiling from source?

Yes but they have set the optimization flags for specific G4 processors. It should make some difference, but who knows exactly how much.
 
Captain Code said:
Yes but they have set the optimization flags for specific G4 processors. It should make some difference, but who knows exactly how much.

and on that note, it is a web browser. its not exactly crunching for primes or anything. it just seems like instead of .5 seconds to load a page it will take .4 seconds. isn't the bottleneck at the download end of things anyway?
 
I tried it on an old G4 I have laying around, and noticed a *slight* difference, but not enough to make it worth messing with.

Just my 2 cents.
 
If displaying HTML pages with JavaScript code never was a big problem anyway, we'd never have discussed browsers' speeds in the first place. Yet, we _have_ for the past three or four years or so - on this very forum. So I'd say it's not entirely unimportant to many users, cfleck. ;)
 
The importance is how much performance does this build offer above the regular build of Firefox, not over Exploder or Safari.

Everyone knows Exploder for Mac has to be the slowest browser ever made, but that's not really what we're talking about.
 
if you really pay attention you can see a slight bump in performance but its not enough to really even be worth it..

if you're one of those people that must squeeze every bit of speed they can out of stuff then go for it. the average user won't notice any difference.
 
Back
Top