Peter Gutmann wrote: > AnilG <a.gul...@tsc.nsw.edu.au> writes: > >> This is really big picture here: I've looked up and suddenly seen Firefox >> market share trajectory looking like we need some steering input fast. This >> is a 3 to 6 year picture of decline so it will take as long to correct. > > Oh dear, this is really going to open a can of worms that probably shouldn't > be opened, I'll try and make this my one and only comment on the topic to > avoid a flamefest, but this does need to be corrected: The unstoppable slide > of Firefox towards a zero market share has nothing to do with HSTS and other > stuff and everything to do with the fact that it's been turned into a bloated > copy of Google Chrome, with an endless succession of disastrously bad > decisions that have progressively alienated more and more of its loyal user > base. If you look at Mozilla's own figures at > https://input.mozilla.org/en-US/, they have a 90% dissatisfaction rating from > their own users (I was going to use a political comparison there but can't > actually find either a politician or corporation who has an approval rating > that low). Slashdot (yeah, I know, but it is a reasonable indicator of geek > opinion) recently introduced a story on Firefox with the comment "for once a > story about a Firefox change that isn't negative". > > I don't think it's worth trying to appeal to Mozilla, because it's a toss-up > whether they'll drop to zero percent market share naturally or drive it to > zero when they discontinue their plugin API (XPCOM and XUL), the only reason > for still staying with Firefox. So the organisation you want to negotiate > with is whoever forks Firefox and reboots it, not the one that's currently > running it into the ground. The "correction" will be when it's forked and > saved by others, in the same way that Phoenix was forked and saved from > Netscape. > > (Apologies to the Mozilla security folks reading this, I know you guys do a > good job on your part of the browser, but seeing Mozilla slowly run their > flagship product into the ground has been like watching a train wreck one > freeze-frame at a time).
I completely concur with Peter here. The situation with Firefox is so frustrating that I feel it's e.g. a waste of time to comment on the <keygen> removal proposal. Because it seems within Mozilla every security code is regarded as obstacle and will be removed anyway in the not-so-long run. Ciao, Michael. _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
