I joined Mozilla just a couple months ago (and honestly I personally was using Chrome a lot before that -- I'm not on the browser team). From what I've seen ta

I joined Mozilla just a couple months ago (and honestly I personally was using Chrome a lot before that -- I'm not on the browser team). From what I've seen talking to people I feel like what the author promotes is what's already been happening. The internal decision process for Firefox has been moving to the UI team, which has been identifying improvements they think are important or easy, and those improvements are getting priority. That's a clear user-centric decision process. As for forking Firefox, it's not something being done explicitly and it's not a clear team, but people are playing around with ideas along those lines and the culture is very open to that process. Jetpack actually has some basis in a split like that (then being brought back to the mainline). No fault to the author, these things are by no means obvious (and I myself can only claim to have a vague sense of what's going on)... but I feel more optimistic the more I know about how decisions and experimentation is done at Mozilla. Sometimes Firefox people come off as very defensive... which I find a little off-putting, but I think it's also a matter of avoiding panic. It would be really stupid to make a long bet on some radical redesign of Firefox, but if you embrace a self-sense of impending irrelevance you can make some really stupid mistakes.