Since I see that a notable VC-famous jerk is now telling us that he wish he'd "stood by" Eich way back, I'd like to tell you a true fact: Eich didn't lose the CEO's job for his (reprehensible) Prop-8 donation.

Everyone wants to believe that's true, because fits nicely into useful narratives a number of invested camps want to champion, whether it's somebody being ousted for reprehensible views or the woke SJW mob somehow pulling down a great leader (tm) but that's not what happened.

At the time, maybe still today, the largest-by-far donors supporting the Foundation were a financially-very-successful gay couple, I believe New York-based financiers whose names escape me, and who IIRC had the ears of a number of other prominent donors. A significant chunk of the Foundation's even-then modest budget came from that, and when this blew up, it put the entire financial structure of Mozilla as a not-beholden-to-shareholders, privately-held-by-a-not-for-profit entity at risk.

After what I'm told was a few days of very difficult negotiation under extraordinary pressure, both internal and external, a deal was struck. The plan was that Eich make an announcement, apologizing for his "mistake" and making some public-benefit commitment about inclusivity, importance of diversity, etc.

Half the board resigned.

But he takes his public drubbing, apologizes and gets his company. The structure of the organization survives, the mission lives.

At the last minute, he reneged.

Now, I have some feelings, still today, about that situation. That bullshit graph he's aired out about Mitchell's salary versus market share carefully omits the fact that he was CTO for most of that time, presiding over a long period of technical stagnation and market decline, and had never directly managed more than a handful of people in his career. It wasn't until years later under new leadership with Firefox 57, the Quantum release, that Firefox became performance-competitive again.

But the real reason wasn't that he made a donation to some reprehensible cause.

The real reason he lost his job was because he showed everyone who mattered that when the chips were down - and I mean, 100%, the whole table is all the way in, down - that he'd put his own pride or vanity or who gives a fuck what ahead of the continued existence of the company and the mission.

He lost his job because he made a bet that he was more important than the possible end of Mozilla and he lost that bet.

When he later announcing his resignation as Firefox module owner and mentioning Brave, he sent mozilla.governance email about how he'd compared other engines to Gecko on all sorts of axes and how Electron/Chromium was superior on all of them, and I can still remember staring at my reply, at the words "if only we'd had somebody at Mozilla for the last fifteen years, in some sort of technical leadership capacity, who might have been able to do something about that. Too much to wish for, I guess".
And one of the few regrets of my time there was that I stared at what I'd written for ten minutes before deciding not to, and deleting it.

Anyway, after getting laughed off the internet for that goofy manifesto of his I'm sure Marca is airing this out now because he'd like to imagine himself also part of some great-man-pulled-down narrative; it's a common affliction among people with so much money they can't feel anything but petulantly-underworshipped anymore and zero useful ideas to speak of.

But that story is bullshit.

@mhoye beware the man who had one highly acclaimed accomplishment early in his career
@mrcompletely @mhoye One that the rest of us have to suffer with ever since.
@mrcompletely @mhoye doubly so when his one accomplishment was making a programming language in a weekend while very likely drunk, and that language is JavaScript
@mhoye I am increasingly unsurprised he went on to found a browser that's some kind of weird arrangement of crypto grift and literally stealing ad revenue
@mhoye also this seems to be as much of a good time as any to remind everyone that Marc Andreesen is also an entire waste of space
@mhoye Do you remember how you phrased it? Snarky or earnest?
@fivetonsflax Nearly verbatim that.
@mhoye @fivetonsflax The "if only we had..." sarcastic/facetious rhetorical style is one I used often in work meetings across a number of employers and customers as a way of connecting and commiserating with like-minded colleagues about the disconnect between intention and execution. My colleagues would begin to anticipate what I might say in similar situations.

@mhoye @fivetonsflax They noticed I only said it in the situation where we had *exactly* the thing I was lamenting not having.

"If only we had some sort of system to track...X" was a regular one in ITIL X-management meetings for X in issue, problem, service, change...etc. it seemed to correlate with cargo-cult X-management.

@mhoye me in my academic library meetings “If only there was a field we could consult that specialized in organizing information….”
(This originally read company-wide, not mozilla.governance, and webkit, not chromium. My mistake, I've corrected those details.)
@mhoye mannnnnnn, Eich literally burned himself on his last email to the company? He literally let the door hit him on the way out? Oh my god, that’s amazing.
@BrendanEich go eat a bag of dicks, you bigoted prick. Apologize for prop 8 funding, donate to LGBTQ equality, or fuck off outta my mentions.
@BrendanEich also, JavaScript? It fucking blows.
@aud @BrendanEich hell yea

go to hell brendan
@BrendanEich if you wanted gay people to be nice to you, you shouldn’t have funded causes denying us equality.

@mhoye Do you have a copy of that email? I don't remember receiving it, but what I'm sure is that the first versions of Brave were actually Gecko-based (using browser.html as the frontend), then Electron then Chromium, but never WebKit.

About Firefox becoming competitive only with Quantum... man, it was so cringe at the time to see the desktop team rediscovering what we learned from the work on b2g (both UI and platform) and that the desktop team fought so much against at the time.

Resigning my mozilla.org project roles

@dbaron @fabrice I misspoke, yeah - it was electron, not Webkit. I'll correct it.
@mhoye @dbaron Also correct that this was almost 2 years after he left, so not a company email...
@mhoye Do you mean this email: https://groups.google.com/g/mozilla.governance/c/dba6C45D9vs/m/eFee27PpFgAJ to mozilla-governance (a public list, from about 1.75 years after he resigned as CEO)?
Resigning my mozilla.org project roles

@mhoye The main factor he cited was web compatibility, which is largely a function of market share rather than technical.

That's not to say there weren't some major technical mistakes. Maybe some of the biggest were:

- not investing more in embedding APIs in 2006-2008
- not understanding and fixing the performance and memory use implications of extensions in 2006-2010 (and fixing widely divergent eng vs mktg opinions of them)

But hard to say if doing better would have changed the result.

@dbaron I suppose I should have specified the time between those things, but I elided a lot of the experience of being at Moz then. The whole leadership/module-ownership question hovering around unanswered for months, the deep schism between the Foundation and the Corporation that went unresolved forever, b2g sucking up all the air in the room, it was all pretty bad.
@dbaron @mhoye not dealing with the ticking time-bomb that was extensions is IMO the most destructive decision that Brendan led and guided Mitchell + the board to... even later 2011-2014. We had a plan to get to multi-process content in 2011 where the key problem was addon compat, and it was an exec-level decision to stop funding that and try to build magic bullets (CPOWs, which were doomed).
@dbaron @mhoye I certainly regret not doing better on extensions fixing; maybe I should have died on that hill in hindsight

@mhoye I also noted in that post:

https://groups.google.com/g/mozilla.governance/c/dba6C45D9vs/m/eFee27PpFgAJ

that for Brave, as a new browser, we chose to prioritize "web compatibility and in particular Chrome compatibility".

No one, neither me nor successor C-levels at Mozilla, could do the same for Firefox, because Firefox faces much higher engine switching costs due to its installed base and features than Brave did in late 2015 when we had not even released yet!

How you could miss this is hard to figure. Rage blinding you to fundamentals?

Resigning my mozilla.org project roles