Slashdot Mirror
Big Changes From Mozilla Mean Firefox Will Get Chrome Extensions
Mozilla announced yesterday a few high-level changes to the way Firefox and Firefox extensions will be developed; among them, the introduction of "a new extension API, called WebExtensions—largely compatible with the model used by Chrome and Opera—to make it easier to develop extensions across multiple browsers." (Liliputing has a nice breakdown of the changes.)
ZDNet reports that at the same time, "Mozilla will be deprecating XPCOM and XUL, the foundations of its extension system, and many Firefox developers are ticked off at these moves."
And for all the right wingers that cry for Eich, saying he wasn't ousted for "not being progressive"? I hate to burst your bubble but he was fired for refusing to do his job simple as that. What IS the job of a CEO? Well a very large part of it is to be "the face of the company" and to deal with the press and issues in the press that are affecting your company's image...what did Eich do? Say "I don't want to talk about it" like a little spineless coward and hid while the opposition could say anything they wanted and build up steam for the boycott because he refused to do his job and fight back! If he would have said "these are my beliefs, this is what I support and what I do not and why" and actually started a dialog? He probably could have diffused the entire thing, remember he had an entire PR team at Moz to help him craft his side, while the other side simply were speaking their minds, so he had a pretty big advantage.
Nope, I don't buy that. Firing him from a company with Mozilla's tech cred for failing to carry out the PR mission sounds like lame after-the-fact justification. I suppose it could be argued that the company's primary focus had already changed by that point--the new marketing CEO and strange decisions since then do seem to point that way--but that makes the situation worse rather than excusing it.
/. post announcing the new CEO:
Eich had already created javacript, founded Mozilla, served as the browser's chief architect and the company's chief tech officer for years and years. It's tough (maybe impossible) to think of anyone more in tune with Mozilla's mission, or qualified to carry it out.
And as we've seen in the last year, "the opposition" has unreal influence over the tech news media (including Slashdot), often right down to user forums/comment policy, including the willingness and ability to spin a one-sided narrative completely disconnected from reality and/or popular opinion.
From the
http://tech.slashdot.org/comme...
We did not "stand by and watch". Many Mozilla staff made public statements supporting Brendan as CEO, including (courageously) many LGBT Mozilla staff. Many more publicly supported Brendan than publicly opposed him. The media of course focused on his opponents because "Mozilla employees call for CEO to step down" gets more clicks than "Mozilla employees support CEO".
http://tech.slashdot.org/comme...
It's absolutely true. There were a bunch of blog posts by Mozilla employees supporting Brendan as CEO (even though many disagreed with his position on Prop 8), all completely ignored by the media. Looking at the relevant date range on http://planet.mozilla.org/ should find them...
Did you ever see any of these viewpoints reported on at tech news sites? I think the Eich fiasco might have ended differently if it happened today, now we're more savvy to the disengenuousness and bigoted (and collusive) nature of those who perpetrate outrage culture.
It's not just a marketing spend. Once word spread around that IE on the desktop was toxic, people sought out an alternative. That same message has not happened (or really been necessary) on mobile. Chrome is the default on Android, and it's a fine enough browser that looking for an alternative isn't necessary for most people. Google has made it easy to sync across platforms, so Chrome has become the new alternative on the desktop as well (for Windows machines only, obviously).
The Firefox situation isn't so much Mozilla's fault for screwing it up as it is Microsoft making real gains in browser quality recently, combined with Google and Safari making for a simpler cross-platform experience. FF is not the default on any major platform, so it doesn't get to use that momentum to press into other platforms. All its major competitors do get that advantage.
The Gecko engine's current extension mechanism is not really compatible with the forthcoming change to multiple processes. (BTW: Multiple processes, not multiple threads, for proper isolation.) This move is in fact _necessary_ for what you want them to do.
Another problem with the current extension mechanism is that any extension can do basically anything to the browser, or any component of it. (Hence the need to deprecate unsigned extensions.) The permission system is a single bit: XUL/XBL chrome (including extensions) can do anything, non-chrome is restricted per HTML5. The new WebExtensions API has fine-grained permissions, among many other good things. See https://wiki.mozilla.org/WebEx... for details.