[citation][nom]jescott418[/nom]This reminds me of AMD when it was losing the battle with Intel over CPU speeds. So it decided to change its model numbers to not reflect at what speed they ran at. I think it was a desperate move for AMD to cover up its failings in developing its CPU's and I think Firefox is doing the same.[/citation]Not even remotely the same. AMD wasn't losing a "CPU speed" battle when they introduced Athlon XP. As a matter of fact, this was around when Intel dumped the steaming turd known as the Pentium 4 on the world. AMD was far ahead of Intel in terms of IPC against the P4. We had hit the point where clockspeed alone didn't tell you anything about the processor's performance (relative to anything other than another CPU in the same family differing only in clockspeed).
Nowadays model numbers are (somewhat necessarily) quite a bit more complex, and only hardware junkies can readily decipher them.[citation][nom]darkxuy[/nom]This is so stupid.I have an idea for them, make the version number after the compilation date (e.g. Firefox 11.08.16), tada! no more version worries.[/citation]So they can only compile once per day? Oh sorry, we left in a crippling bug in our forced-update, it's really easy to fix but we can't do anything because we already compiled it this morning. Yeah, we'll need you to wait for tomorrow, mmkay? Or maybe they have two versions, with internal version numbers, but with the same end-user-visible date_version?
What's so freaking wrong with a version number? Even if it's just a freaking build number stored in About?