251–260 of 322 posts
Thank you to everyone who has ever worked on MDN or contributed at any capacity.
Earlier quoted context omitted.
Do you apply the same rigorous standards to all your purchases? Do you refuse to buy a drink or a pair of shoes or a travel ticket unless you can ensure that "not a single cent goes to execs" who get "absurdly high, grossly underserved salaries while they butcher the company all the way down"? Or do you think the Mozilla execs are _uniquely_ greedy to a degree not comparable to that of the execs of Nestlé, Nike, etc.…
It isn't just "Mozilla Execs", it's specifically Mitchell Baker[1] because of: > " In 2018 she received a total of $2,458,350 in compensation from Mozilla, which represents a 400% payrise since 2008.[14] On the same period, Firefox marketshare was down 85%. When asked about her salary she stated "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 ti…
Using the same timescale as the Wikipedia article, 2008 to 2018, Mozilla's revenue had risen from $78.6 million to $436 million. A more than 400% increase. Does that justify her salary?
This is an interesting take on documentation - mainly because I fail to see the value proposition in paying for the functionality provided. Speaking from my own experience: - Notifications. I am not sure that I've ever needed to know when a doc is updated, because if there is anything radical coming on the market (or in a spec proposal), there are other avenues to find out about it. - Collections. That is already a f…
The other day I wanted to learn Svelte. Even though the tutorials on the Svelte homepage are great, I found the MDN Svelte tutorial to be better: it explains the conceptual differences wrt other frontend frameworks well, it explains in detail how to enable Typescript and migrate your projects, and it has a dedicated section that describes different deployment options. While of - of course - all of these infos can be…
I'm curious how often people are needing offline access to documentation for web development.
It's much more useful for specific API docs rather than general "how do I do X" stuff but it's very nice. Helps that you don't have to deal with scrolling through stuff like web3schools.
Earlier quoted context omitted.
It's documented to do so, and it works for me. What part isn't working for you?
It just doesn't revert to the old download. As I said, the first thing I did when I saw the release notes was checking how to go back to the old settings. I tried that on 2 computers, both using linux (Ubuntu and PopOS), without any luck. It doesn't ask me anymore what if I want to open the file or save it.
I hope it eventually works for you -- I also prefer the old behaviour when doing multiple downloads in quick succession.
Earlier quoted context omitted.
It isn't just "Mozilla Execs", it's specifically Mitchell Baker[1] because of: > " In 2018 she received a total of $2,458,350 in compensation from Mozilla, which represents a 400% payrise since 2008.[14] On the same period, Firefox marketshare was down 85%. When asked about her salary she stated "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 ti…
>What have other CEOs done to justify their salaries? Using the same timescale as the Wikipedia article, 2008 to 2018, Mozilla's revenue had risen from $78.6 million to $436 million. A more than 400% increase. Does that justify her salary?
"(2) Retention bonus to compensate Sue for lost opportunities during the transition period: $165,000."
This seems to undermine Mitchell Baker's reasons for her salary increase, doesn't it?
Wikipedia also gets a slightly higher score from CharityNavigator than Mozilla, edging them out on more efficient earnings, lower admin overhead, but far ahead on "growth of expenses": https://www.charitynavigator.org/ein/200049703 vs https://www.charitynavigator.org/ein/200097189
[1] https://en.wikipedia.org/wiki/Wikipedia:Fundraising_statisti...
[2] https://wikimediafoundation.org/about/financial-reports/#sec...
[3] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_salarie...
[4] https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@list...
Fundamentally, maintaining MDN is costly because of the rate of instability in rapidly changing browser APIs. Those APIs change quickly and inconsistently because they’re managed by a centralized cabal of a few corporations with a combined multiple trillions of dollars in market cap. And yet, somehow it’s Mozilla, the browser vendor with the least money, that ends up saddling the cost for MDN. Why is this? In general…
Their biggest competitor is a major, no?
I like the idea! While I do not need these premium features I wanted to hit the "sign me up" button instantly just to support them. But then I found out that there's no such button and my country is not on going to be supported anytime soon. And if MDN people are reading this: consider adding an "enterprise" option with centralized account management.
I find the regional availability odd for a product like this. What could be the reason? Maybe payment processing, or i18n?
It's especially hilarious when their vpn products only available for select countries, but their vendor (Mullvad) accept purchases from all countries.
Earlier quoted context omitted.
>What have other CEOs done to justify their salaries? Using the same timescale as the Wikipedia article, 2008 to 2018, Mozilla's revenue had risen from $78.6 million to $436 million. A more than 400% increase. Does that justify her salary?
Using the same timescale, Wikipedia itself (the Wikimedia Foundation) went from $5M revenue to $120M, 24x. [1],[2]. During that time the Executive Director's salary went from $168k to $387k[3]. At the end of Sue Gardner's leadership in 2014 there was a question about her $300k salary[4] which included the response: " (2) Retention bonus to compensate Sue for lost opportunities during the transition period: $165,000.…
They're not really comparable organizations. The corporate comparisons you started with were closer comparison, though Mozilla has some unique circumstances.