How Mozilla Firefox is Falling Behind
Mozilla Firefox, an open-source web browser, used to be the coolest kid on the block. It was much speedier than Internet Explorer and it was much more stable and secure than Internet Explorer. This wasn't very long ago, either. I would say about a year or two ago, Firefox was the top dog. While Internet Explorer remained on top with plenty more market share, Internet Explorer was mainly for all those non-tech savvy computer users, and it still is.
Firefox 3.0 was even a bigger success from Firefox 2.0 with great new technologies, much faster, and new features of course. The problem came about when delays kept coming for Firefox releases. When Firefox 3.5 was planned to be released a couple months before it actually was released -- same scenario with the current version, Firefox 3.6. So Mozilla got the reputation of not being able to keep up with their word.
Plus, in 2008, Google introduced its own browser, Google Chrome, but it didn't really get that much spotlight until about Google Chrome 3.0. It really started to pack in some useful features and technologies, while still maintaining a simple interface and it was claimed to be the fastest browser on Earth. This was Firefox's opportunity to integrate that speed and technology into their browser, but they didn't. They had only had plans for all that great stuff maybe in Firefox 4.0. We're waiting and waiting... why not just slam that stuff in now?
Firefox's market share in the past few months has began to decline as they fall behind, the speed is far slower than both Google Chrome and Safari 4. It's faster only than Internet Explorer. They still are far behind in supporting aspects of HTML5. And they still have that old style Windows XP look and feel to the user interface going on, ever since Firefox 2.0 and even before that. It is said that they are working on Firefox 4.0 with a new design, but that isn't planned until late 2010 and in Mozilla's world, that's in first quarter of 2011.
The point of this whole article? Firefox needs to step up their game or they will slip into Internet Explorer's ways. They are taking too long to make a better browser, when Google Chrome is constantly being updated on. It's time to stand your ground, Firefox, because 25% of PC users ditched Internet Explorer, and they can ditch you too.







Just sayin...
And it's easy to be the fastest one when not even all basic functions are implemented and active!
And chrome is really stepping up podium!
Complaining about not getting 1900/100 on Acid, while being totally clueless about the value of what's missing. (Yeah, you really miss those SVG fonts, do you?)
A quick list of what Firefox has pioneered the last 3 years:
- WOFF fonts (way more important than SVG fonts in Acid3)
- WebGL (Mozilla and Chronos)
- Hardware accelerated Video, canvas and SVG (yep, Mozilla started this before MS)
- ECMAScript 5th edition. SpiderMonkey is furthest along of all browser JS implementattions. Very close to 100 % support for strict mode.
- ECMAScript harmony proxies and ephemeron tables (the latter will be renamed to something understandable)
- Grouping selectors with the -moz-any() selector
- Using any element as background (-moz-element())
- Usable syntax for gradients, close to what will be the W3C standard
Etc
And most important. Everything in Firefox is being implemented with rigorous quality, including accessibility. Chrome has zero accessibility. It does 0% ARIA. Every single so called HTML5 control has zero accessibility.
In fact, I've written about this recently.
http://itpastorn.blogspot.com/2010/07/no-browser-supports-html5-yet-part-1.html
http://itpastorn.blogspot.com/2010/07/no-browser-supports-html5-yet-part-2.html
When Acid3 was released, indeed even before it was released, Safari and Opera had a race to be the first to 100, pass the rendering test and the "smoothness criterion" - the latter being a really artificial score about speed with almost no bearing on real world web site performance. In so doing I could clearly observe Webkit developers cutting quite a few corners just to win the race. (I tracked this in their Bugzilla. I could not track Opera equally wll, since they are closed source.)
One example is SMIL. In order to achieve a point in Acid3 you really only need some very rudimentary support, not at all usable in any real world scenario. As soon as that rudimentary support was implemented, the bug was closed immediately. The corresponding Gecko bug, OTOH, was kept open for ages.
This is yet another illustration about the peril of putting too much emphasis on Acid3, when comparing browsers. Having an Acid3 score of 50 is definitely not good, but 2 browsers being withing 10 points of each other, well that's just numbers.
(Since Webkit got its 100/100 on Acid3 they have really improved their SMIL support, so today it is very complete.)
I chose not to comment on the other blog post, since it is mostly about the UI. When it comes to UI every browser is trailing (and trying to mimick) Opera, IMO. And personally I'm a fan of the status bar. But all this is just taste, and everyone is entitled to his or her own. That's the best thing about having browser choice.