Dutherenverseauborddelatable

(disclaimer; it's my blog post)

I don't think it is - this post by yoric goes into some detail as to why killing embedding in its previous form was a good idea: https://dutherenverseauborddelatable.wordpress.com/2016/03/07/the-gecko-monoculture/

I do think it was a poor decision not to support EmbedLite more fully, but looking at bugs in Bugzilla, that appears to have been down not only to Mozilla's general direction, but also the decisions of individual engineers, with what looks like sane reasoning (that I partly disagree with, but then I'm likely not privvy to all the facts).

Hindsight is 20/20, it's easy to point at mistakes that have already been made and there's not much we can do except learn from them. What I'm really worried about is that we've committed to this 'no embedding' path purely out of apathy to change it now. The sort of "Oh, it's a really big job to do anything now, we don't have the resources so we're not going to bother".

yoric makes the excellent point that we're significantly cutting down our potential platform engineer employment pool. Much like him, I was also hired because I was working on embedding Gecko, and thusly, Gecko platform. I fear that we're going to miss out on whatever the next big thing is because we're not enabling people to use our (really rather good, and liberally licensed) technology, and that we're not going to be in a position to keep up with our competitors because we can't offer anything compelling to the people with the…

The Mozilla FAQ on CEO Resignation says "Brendan was not fired and was not asked by the Board to resign. Brendan voluntarily submitted his resignation. The Board acted in response by inviting him to remain at Mozilla in another C-level position. Brendan declined that offer. The Board respects his decision." [1]

"Another C-level position" definitely means not CEO, and probably means CTO.

So Brendan is not disagreeing with the posting, he's just not stating that he was offered a job as CTO or whatever.

I don't know where cpeterso got the idea they asked him to "stay the course as CEO or CTO", but the FAQ makes it pretty clear he was not asked to stay as CEO, and was probably offered his CTO job back. Are there any other "C-level positions [2]" that he is qualified for? Probably not CDO. ;)

Edit: cpeterso may have been quoting yoric from here: [3] So I don't know where yorik got that idea from. But Brendan corrected his incorrect information, without actually openly revealing what the correct information was.

[1]: https://blog.mozilla.org/blog/2014/04/05/faq-on-ceo-resignation/

[2]: https://en.wikipedia.org/wiki/Corporate_title

[3]: http://dutherenverseauborddelatable.wordpress.com/2014/04/07/a-curse-and-a-blessing/

Unfortunately, this technique is not guaranteed to work. Even if you write, flush then rename, the OS and disk may decide to apply these operations in a different order, breaking your guarantee.

A few years ago, I had to fix this behavior on Firefox, because it was actually causing data loss. The only techniques I found that seem to work are journaling and rolling backups + transparent recovery (which can still lose data, just one order of magnitude less often).

If you're interested, I wrote about the latter in this blog post: https://dutherenverseauborddelatable.wordpress.com/2014/06/26/firefox-the-browser-that-has-your-backup/

The "temporarily hung interface" is definitively one of the worst things about Firefox. Fortunately they recently set up a project dedicated to fix it, next releases will probably behave much better. A few links for those interested

https://dutherenverseauborddelatable.wordpress.com/2013/04/10/announcing-project-async-responsive/

https://dutherenverseauborddelatable.wordpress.com/2013/04/26/project-async-responsive-issue-1/

https://dutherenverseauborddelatable.wordpress.com/2013/05/24/project-async-responsive-issue-2/

https://dutherenverseauborddelatable.wordpress.com/2013/06/05/project-async-responsive-issue-3/

I was glad to read this, but then today I noticed a new comment by Eich clarifying that no one tried to convince him to stay as CEO.

http://dutherenverseauborddelatable.wordpress.com/2014/04/07/a-curse-and-a-blessing/

Perhaps your understanding is a little off. Maybe it's a prudent position to go back to not really knowing what happened between Eich and the board.

Anyway, I'm done being angry at Mozilla. You guys are doing an important thing. Calls for a boycott are counterproductive and will only hurt us all. What's done is done.

I just can't quite find it in my heart to support you anymore.