You are correct. In my haste to express the idea that they make more money off games than they do consoles, I went overboard in stretching the "initial loss" meme.

No clue what's causing it, but see what plugins are being loaded? HP added a bunch of crap to my installation that brought it to a crawl.

If that doesn't work, may I suggest bugzilla?

You'll have to get addons for both. They want to phase out the status bar, and they figured not providing that functionality was for the best. The titlebar is part of an ongoing WONTFIX, because they think Tabs on Top deserves more love. Thankfully, tired of people's complaints, they whipped together this addon that does the trick: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Faddons.mozilla.org%2Fen-US%2Ffirefox%2Faddon%2F221514%2F (Vista+)

Most consoles are sold at a loss - the manufacturer makes most of their money from game licensing. By buying a Sony product, he'd eventually contribute to their bottom line by buying a new game (used ones seem to be getting more and more gimped).

Can you define bloat (in the context of Firefox) without pointing at nebulous things such as the amount of RAM the OS has allocated for it?

According to http://www.arewefastyet.com/, they're beating Chrome in Sunspider. That, plus their graphically accelerated rendering + compositing makes their Windows builds quite speedy.

Conversely, Mozilla, Opera and Google want to support Theora and WebM, but Apple refuses.

You keep using that word. I do not think it means what you think it means.

How about ECMAScript? ;-)

Show me where h264 is a requirement in the HTML5 spec.

kthx.

They probably couldn't figure out a way to switch it to "Blow".

What about having a strcmp that compares strings using a randomized series of indexes?

E.g.

compare position 4, then 1, then 3, then 10, etc.

In addition to what the above poster said, they aren't putting all of their eggs in one basket. They've been heavily focused on making sure the entire UX is fast/responsive, not just benchmarks.

Hovering over a datapoint should show which engine is being tested.

For those of you who want to track the progress of Mozilla's JS efforts, visit the self-descriptive ARE WE FAST YET?