3 ms·

Micro-Optimizations are bad? That is just a load of shit. If you can prove that Firefox's optimizations actually make incorrect results in any way, I am 100% b

Micro-Optimizations are bad? That is just a load of shit. If you can prove that Firefox's optimizations actually make incorrect results in any way, I am 100% behind whoever claims that micro optimizations are bad. However by firefox making them it means that I don't have to worry about the nitty gritty details about what order of instructions will perform better without changing the code. Or things like loop unrolling that don't have to be done in my checked in source. Yea I think this argument is about 30 years too late... If anything this proves FF3 is awesome. Regarding web standards... As much as I am 100% for having good web standards, what good is adhering to a standard when no one can use it. I use the acid tests as an indication that browser x, y and z are browsers I want to be supporting. Unfortunately I always have to support IE... Sometimes even IE6, so acid tests are just nice-to-haves at this point. I just can't wait till IE7 completely dies (hopefully it won't be as long as IE6).

ahoyhere 17y ago
> However by firefox making them it means that I don't have to worry about the nitty gritty details about what order of instructions will perform better without changing the code Actually, Firefox benefits the most from tweaks like this, because its engine is so slow. For whatever reason. That's why I thought this post was interesting!
- GrandMasterBirt 17y ago
  A good point. If the FF engine is so slow it needs this, then the engine needs help. However I see no reason why you should not be able to indicate to firefox that for this page do not optimize the javascript, then vuala good debugging. The only catch is that the optimizations need to be proven to be correct in all cases. Once we have Safari for Linux I will consider using it as the main browser... Scratch that, once at work we officially support it ill consider it :)
rufo 17y ago
Micro-optimizations aren't bad for users, but they can be bad when you're debugging. The source code you wrote is not necessarily the source code that Firefox displays to you.

ahoyhere 17y ago

> However by firefox making them it means that I don't have to worry about the nitty gritty details about what order of instructions will perform better without changing the code Actually, Firefox benefits the most from tweaks like this, because its engine is so slow. For whatever reason. That's why I thought this post was interesting!

GrandMasterBirt 17y ago
A good point. If the FF engine is so slow it needs this, then the engine needs help. However I see no reason why you should not be able to indicate to firefox that for this page do not optimize the javascript, then vuala good debugging. The only catch is that the optimizations need to be proven to be correct in all cases. Once we have Safari for Linux I will consider using it as the main browser... Scratch that, once at work we officially support it ill consider it :)

rufo 17y ago

Micro-optimizations aren't bad for users, but they can be bad when you're debugging. The source code you wrote is not necessarily the source code that Firefox displays to you.