It is a shame though cause this is kind of a decent write-up.
It is a shame though cause this is kind of a decent write-up.
For Mozilla, technology in this case was not more important than community values. Postgres and Linux have technological improvements, but I'm eager to see the tech industry be far more self-aware in trying to progress in its social issues, rather than just progress with features.
Plus, this was a struggle and many on these forums were affected. The underlying causes won't go away after one day, and more worryingly, perhaps not for years to come.
With this inspiring precedent, we can have confidence that the next CEO of Mozilla --and every other company, we hope-- will be well vetted to hold the correct behaviors -- the only, obviously morally correct behaviors-- toward the great challenges of our time: women's abortion rights (or is it fetuses' birth rights?), animal abuse rights (factory farm supporters are unfit to lead), gentrification (wealthy SF residents displace evicted tenants, ruining their lives, so they are not leadership material), ...
All of which says that the community of which mozilla is a part is particularly sensitive to slights against gay people. This should have been, oh, completely unsurprising.
And the ceo is often symbolic in a way that a cto isn't.
And in particular, I wouldn't work for firefox while he was ceo. He made a donation specifically intended to maliciously hurt my friends and neighbors. I can't support that.
Where the fuck did you get that idea? You just made that up. You don't know his specific purpose, you may think you can infer it but you certainly don't know it.
Furthermore, there is not a scintilla of evidence to suggest he acted out of malice. It is far more plausible that he considered gay marriage inconsistent with his religious beliefs and that he also felt compelled by his religion to defend his view of what marriage should be.
2 - because i'm not deliberately obtuse or stupid
Would things have changed if he made a big direct apology instead of mumbling something about "causing pain" buried in some blog post? Could Mozilla have done X or tried Y instead? I think we're going to be dissecting this for a while.