Mozilla was actually founded under similar circumstances. I hope engineers who work on the core product (and those who were let go) are talking about another reincarnation of Firefox - from the same code base but with different leadership.
Mozilla was actually founded under similar circumstances. I hope engineers who work on the core product (and those who were let go) are talking about another reincarnation of Firefox - from the same code base but with different leadership.
There are valid criticisms you can make of Baker (see the compensation issue discussed elsewhere in these comments) but "She has the wrong degree" doesn't seem like one of them, unless you think that Mozilla engineers - the people doing the deeply technical work - must be required to have a CS degree.
Mozilla needs a CEO who can understand its technology and its partners (developers) at a very fundamental level. Mozilla needs a Lisa Su.
That sounds like pretty solid technology industry experience for an exec, no?
For example in my tech related company, the HR folks know little beyond Word and Excel despite some having worked for years there.
What were her roles up to now?
President and founder of the Mozilla Foundation 2003 onwards, and also previously CEO of the Mozilla Corporation 2005-2008. Also she wrote the Mozilla Public License before that. I suspect she knows a little bit more than Word and Excel.
Seriously - go criticize her for her salary, or failure to execute, or for-profit vision, or something. There's lots of criticisms that can be actually substantiated. The hypothesis that she doesn't understand what Mozilla is requires significant evidence. It's entirely possible a Mozillian could show up and say that actually she's been a clueless and politically savvy leader, but outsiders speculating that she can't possibly be qualified need to provide more than speculation.
I am well aware of her tenure and good work at Mozilla (from public sources). The argument I was making was that the failure to execute is correlated with not understanding technology well enough. Certainly not claiming that's the only factor, but it might play a part in it.
How will you make expensive long-term bets otherwise? The proof is in the execution, or the mis-execution.
1. Mozilla retired Firefox OS in 2016/17. And in a couple of years, a fork of it (KaiOS, which shares 95% of the same code) gets pre-installed on upwards of 80 million (probably more) units. It could have been a lot more if the OS was better; it really had a shot at low-end phones and TVs.
2. If the team says they need to commit tens of millions of dollars and half a decade or more to create a new, safe programming language for browsers and a prototype - will the CEO approve? And if yes, wouldn't it have been entirely based on advise from others in the room?
3. The world needs an efficient browser engine for multi-core devices coming with bundled GPUs. Requires nearly a decade to get right - how does one commit to that unless the complexity (and not just the rewards) are fully understood?
4. The failure to sell the Servo vision (safety, multi-core) to device manufacturers ultimately rests on the CEO. Instead, the Servo team got axed.
Every technology company needs a CEO who deeply understands the technology.
https://en.m.wikipedia.org/wiki/Sundar_Pichai
So unless I’m missing something he does not have a CS background or software engineering experience, and, presumably, was yet able to acquire at least some understanding of computing.
I expected the CEO of Mozilla to have experience with software engineering.
The fact that MDN, Servo and Dev Tools team got the guillotine instead of execs and marketing speaks for itself.
That's my point. Let it speak for itself. It's entirely possible for someone to be an adequately qualified CEO and also just be bad at the job, that's an argument you can make.
But here's an example: Mozilla folded part of the Servo team into the Mixed Reality team earlier, and now they have been let go. Many people (incl me) thought that an efficient engine such as Servo will play a big role in the future of Mozilla, with devices going multi-core and apps with embedded browser engines (like Slack, Teams) becoming mainstream. And now, we're at a dead end. The quality of talent that was let go is stratospheric, as you can see from all the interest in hiring coming from various companies.
The whole thing has flopped and the browser has lost market share, and if I were Mitchell Baker I'd seriously question my ability to lead Mozilla. She can play senior roles in many companies including Mozilla, but not the CEO.