It's like Apple comparing iOS to Symbian and lauding how great iOS is, when really they should be watching Android.
Adopting a process-per-tab model is currently being implemented (https://wiki.mozilla.org/Electrolysis), and I imagine once that's done we will be discussing Chrome a lot more.
Based on my experience, Mozilla has a lot of reasons to be afraid of Chrome.
http://www.mozilla.com/en-US/firefox/beta/
We are nearing the end of our Firefox 3 cycle (Firefox 4 is going to be released next month), and that's where our significant speed improvements have been implemented in the last 2 years. It's about even with Chrome speed-wise.
Obviously I wasn't suggesting you weren't watching Chrome at all, but it's good to hear you're making the right decisions in competing with Chrome (primarily the reduction of Firefox's inherent clunkiness and slowness).
There's been several articles about this:
Its actually good enough to never have to worry about moving to a different browser (If its what you are using).
Chrome: 10.0.648.45 dev
HTML5 score: 293 FF4: 255
Compatibility differences from [1]:( "-" == in other category )
Chrome 10 FF 4
Partial:
CSS Text-Overflow
Datalist Element -
WAI-ARIA -
SVG for HTML -
SVG filters -
- h264 video
- Web notifications
- SVG fonts
- Web SQL
- WebSocket
- HTML5 Form
Complete:
Server-sent DOM events
CSS Text-Stroke
Progress & Meter
h264 video -
CSS masks
Web notifications -
SVG fonts -
Web SQL -
CSS Animation
WebSocket -
HTML5 Form -
Form Validation
- Datalist Element
calc() in CSS
Animated PNG
- WAI-ARIA
- SVG for HTML
- SVG filters
Summary:
87% 81%
And WTF are they doing with that table[2] (disable "detailed tables")? It doesn't render correctly on anything I've got (OSX).[1]: http://caniuse.com/#agents=firefox,chrome&eras=near,unof... [2]: http://caniuse.com/#agents=firefox,chrome&eras=near,unof...
I was an avid FF user for many years. I shied away from Chrome for quite some time, until this December. A fresh FF install with no addons was painfully unresponsive, given 'too many tabs'. Those same tabs in Chrome chugged along.
I hope FF can get back on track(relative to Chrome:P) and reduce some of the bloat.
in my completely unqualified opinion, i'd have guessed they'd be better off persuading the growing wave of users who are switching from firefox to chrome.
A recent one: an input field would be spontaneously filled with a "1" if (and only if) Firebug was active. Persisted across application re-starts, but not through a reboot.