Only 25% of Firefox Downloaders Are 'Active Users' 294
bheer writes "The Guardian points out a page on the Mozilla wiki noting that 'only 50% of the people downloading Firefox actually try it out, and only a further half of those continue to use it actively.' ZDNet has some commentary on the browser's retention rate. While a 25% retention rate isn't necessarily bad, Mozilla is trying to improve these figures with a 12 point plan that includes more TV and media advertising, a better start page and several installation tweaks."
Re:Why download? (Score:3, Informative)
I'm not surprised. (Score:2, Informative)
If these are the kind of people they're losing, I'm not all that upset about it. Too many people assume that their homepage is part of their browser. I tried to explain to him that yahoo only opened up as default on IE because it was set to be his homepage and that I could do the same thing with Firefox. He then made up some excuse that he's fine with IE and doesn't need to change.
So, the two problems Firefox is facing are:
1) Stupid people
2) People feeling they don't *need* to change and therefore use that to say they shouldn't.
Re:That's still a lot (Score:5, Informative)
Re:This is SO ironic!!!! (Score:2, Informative)
No. This is popular misinformation. From the Roadmap:
Mozilla never was bloated, that's something the Firefox fanboys and fangirls made up.
Re:That's still a lot (Score:4, Informative)
MSN Messenger uses IE when it needs to past things through HTTP POST, eg. to authenticate you as Curtman123@hotmail.com to MSN Spaces. This is necessary because there's no real standard way to pass HTTP POST to the default browser over the command line. I think some other clients have got around this in the past by making a temporary HTML file, having code to send the HTTP POST and then opening that in the default browser. For links in MSN messages, I find they all go the default browser.
Re:Seems fallacious (Score:1, Informative)
You thought wrong. By default, Firefox phones home at least twice a day.
To see that this is true, go to your about:config and look for things like extensions.blocklist.enabled, extensions.blocklist.interval, and extensions.blocklist.url. Or check out extensions.update.enabled, entensions.update.interval, and extensions.update.url.
Hint: 86400 = 24 * 60 * 60.
Re:That's still a lot (Score:3, Informative)
The Vista Hardware Compatibility List [microsoft.com] claims to need IE6 or later; apart from some minor rendering issues, it worked fine with spoofed Firefox. (What kind of moron would make a list IE-only, anyway??)
Re:image resizing (Score:1, Informative)
Ok well it's still not that complex at all:
URL: about:config
type: image_r
set to: false
Step 3: Profit.
Re:That's still a lot (Score:3, Informative)
The Camino guys just have higher quality standards. IMHO Camino alpha releases are often so good that they could be called final releases.
The one guy hired by MoCo to work on FF for Mac is currently not working to improve the Mac experience. No, he's working on not sucking even more.
Gecko/Mozilla Plattform 1.9 will use Cairo which up to the latest FF3 alpha works really really bad on Mac OS X. If you think that FF2 has issues on Mac, you should try that alpha release. It's horrible on Mac. You get Aqua buttons but that's about it. I know, it's an alpha and alphas are allowed to suck, but right now the current builds of FF3 don't even display many italic fonts. Think about it: The FF Mac guy works almost exclusively to fix Cario bugs on OSX. He's not working on Keychain integration and so on.
So for the final release we can be lucky if FF3 won't have MORE bugs on OSX than FF2. You can expect that italics will work again, that arabic text will work again, but actual improvements in the Mac departement compared to FF2? I highly doubt it.