Earlier quoted context omitted.
"I don't like something so no one should use it!" What kind of logic is that? I actually prefer going to w3schools because as a quick reference I find what I'm looking for much faster than MDN. It has interactive examples right at the top so you can get a quick idea on what a function does. I am happy that both exist. Either you are completely out of touch or you're going to need to show some of the "low quality" exa…
1. where did you see that logic? I can't see it in the comment 2. w3schools has surface-level tutorials that teach you the most basic use case of each feature. It's decent for teaching, hence the name. MDN on the other hand is a complete reference - it shows every possible way to use a certain feature in a standardised format. Not as beginner-friendly, but it's what professional web developers need. They are very dif…
Mozilla and Open Web Docs Working Together on MDN
41–50 of 103 posts
Re: Mozilla and Open Web Docs Working Together on MDN
#42Earlier quoted context omitted.
"I don't like something so no one should use it!" What kind of logic is that? I actually prefer going to w3schools because as a quick reference I find what I'm looking for much faster than MDN. It has interactive examples right at the top so you can get a quick idea on what a function does. I am happy that both exist. Either you are completely out of touch or you're going to need to show some of the "low quality" exa…
As someone who's done webdev for a living since 1998, I share the OP's distaste for w3schools -- they truly earned their notoriety as a low-quality, spammy, SEO-hacking parasite. It was so bad it inspired a large group of some of the biggest names in the field to push back with a site called "w3fools" that tried to set the record straight and steer the hapless masses away from w3schools. See eg https://web.archive.or…
Re: Mozilla and Open Web Docs Working Together on MDN
#43Earlier quoted context omitted.
That's because donations will never even remotely cover Mozilla's costs. They get something like $3m in donations. Wikipedia gets something like $120m. Mozilla's costs and Google income are like $400m.
Is a browser so expensive to maintain? $400m/year?
Re: Mozilla and Open Web Docs Working Together on MDN
#44Earlier quoted context omitted.
"I don't like something so no one should use it!" What kind of logic is that? I actually prefer going to w3schools because as a quick reference I find what I'm looking for much faster than MDN. It has interactive examples right at the top so you can get a quick idea on what a function does. I am happy that both exist. Either you are completely out of touch or you're going to need to show some of the "low quality" exa…
As someone who's done webdev for a living since 1998, I share the OP's distaste for w3schools -- they truly earned their notoriety as a low-quality, spammy, SEO-hacking parasite. It was so bad it inspired a large group of some of the biggest names in the field to push back with a site called "w3fools" that tried to set the record straight and steer the hapless masses away from w3schools. See eg https://web.archive.or…
Re: Mozilla and Open Web Docs Working Together on MDN
#45Earlier quoted context omitted.
That's because donations will never even remotely cover Mozilla's costs. They get something like $3m in donations. Wikipedia gets something like $120m. Mozilla's costs and Google income are like $400m.
Is a browser so expensive to maintain? $400m/year?
> For 2019, the Mozilla Foundation received $15,858,258 per a trademark license agreement with Mozilla Corporation, allowing us to reinvest earnings from our products into advocacy and grant making that grow the internet health movement.
Re: Mozilla and Open Web Docs Working Together on MDN
#46A better example is Newman's Own. Their mission is not to make the world's best tomato sauce. That is just how it makes money.
Mozilla needs to find its tomato sauce. Then Firefox and MDN can become the recipient of funds, not the source.
Re: Mozilla and Open Web Docs Working Together on MDN
#47Earlier quoted context omitted.
I agree that pages about web development should themselves not depend on CSS3 support at the renderer because it's a huge step forward from CSS2 and the documentation itself is just simple documents rather than complex layouts. This has the air of web designers not having even considered this aspect and just went with modern web standards as usual. So an issue should maybe be raised about this. As I browse the site,…
Instead of creating a new tool to convert MDN's content into HTML, it would probably be easier to modify the official tool, Yari, in order to produce web page with more compatible (and faster) CSS & JS. https://github.com/mdn/yari But I don't think it would be useful unless MDN merges in the changes. My daily web browser struggles with the new MDN rendering unless JS is disabled. So I've lost a few features since the…
Re: Mozilla and Open Web Docs Working Together on MDN
#48Re: Mozilla and Open Web Docs Working Together on MDN
#49Earlier quoted context omitted.
There isn't even a way to donate. All "mozilla" donations go to the foundation and their social justice causes, not useful things like MSN and Firefox.
That's because donations will never even remotely cover Mozilla's costs. They get something like $3m in donations. Wikipedia gets something like $120m. Mozilla's costs and Google income are like $400m.
Re: Mozilla and Open Web Docs Working Together on MDN
#50For now, it is impossible to tell whether a given code snippet is licensed under CC0 or MIT.
Good luck using code from MDN.