What would be the best way to download MDN for offline use? A quick search shows:
https://developer.mozilla.org/media/developer.mozilla.org.ta...
https://kapeli.com/mdn_offline
https://zealdocs.org/
Any experience with the above?
Documenting the Web together
131–140 of 212 posts
Re: Documenting the Web together
#132Earlier quoted context omitted.
Because video-games is still the one place where Mac and Linux are lagging behind, and they have DirectX to thank a lot for that.
So, MS isn't new, it's same old MS, and their good behavior happens only when they already lost their monopolistic grip. Q.E.D.?
Privatize the profits, socialise the losses. This is why commercial companies cannot be trusted to sustain a wiki, open source, or free software model.
Re: Documenting the Web together
#133What would be the best way to download MDN for offline use? A quick search shows: https://developer.mozilla.org/media/developer.mozilla.org.ta... https://kapeli.com/mdn_offline https://zealdocs.org/ Any experience with the above?
Definitely https://devdocs.io
Re: Documenting the Web together
#134What would be the best way to download MDN for offline use? A quick search shows: https://developer.mozilla.org/media/developer.mozilla.org.ta... https://kapeli.com/mdn_offline https://zealdocs.org/ Any experience with the above?
If you are on macOS, then Dash (by Kapeli) with the CSS/HTML/JavaScript docsets is your best bet. Having offline docs available at the speed of my fingertips throughout your OS has been a fantastic productivity booster for me. I'm not a heavy MDN user, so I don't know if there's anything that's not covered by the above three docsets.
If you are on Windows or Linux, then Zeal and Velocity are basically the same thing (they're only available on platforms where Dash isn't). Zeal's search used to be pretty bad, but at least you have the option to send Pull Requests on GitHub.
Re: Documenting the Web together
#135The is great indeed. I hope w3schools.com won't appear in Google search result. BTW, It feels like OP omitted to mention to MS in the title though.
I barely webdev, but when I do, I've found w3schools pretty helpful. What's wrong with it?
Historically, w3schools had a lot of outdated (or outright wrong content):
Re: Documenting the Web together
#136Don't forget you can use https://devdocs.io/ too which also searches MDN and store offline. The two are a great pair.
While we're on MDN related awesomeness, shameless plug: Back when I was in school, I made this Chrome extension which allows you to jump directly from the address bar to the MDN page you want:
https://chrome.google.com/webstore/detail/mdnjump/mfjekjhknp...
Re: Documenting the Web together
#137My favorite line was this:
One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering.
It wasn't favorite because I agree with it. It was favorite for the humor value of Microsoft accepting a principle that flies so strongly in the face of how the company established itself, managed its battles with competitors, and tried to sabotage existing web standards for most of my professional life.
I'm glad they are finally claiming to be on board. I'll trust them as far as I can throw them. (Guess how far I can throw 120k people...)
Re: Documenting the Web together
#138This news sounds great to me, but I feel like I don't understand what's happening behind the curtain and don't grasp the second-order consequences. What would motivate them? I wonder what the political motives are (industry politics, not the other kind that we won't mention here). Could this eventually displace standards bodies such as WHATWG and W3C? If the Product Advisory Board of Mozilla, Google, and Samsung agre…
Complements and substitutes: https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
Modern web companies don't make money from the web, they make money from something you do while you're on the web. The less the web costs to use (in the broadest possible sense of cost), the more people will use it, the more money they will make.
That's why Facebook's trying to pay off Indian ISPs, and Google's pouring money into web browsers and internet balloons. Microsoft came late to this party because their original make-money-from-the-OS model meant they were trying to compete using the browser, but now that they have a cloud strategy like everyone else, the law of complements has turned them into good web citizens too. Thanks, Satya!
Re: Documenting the Web together
#139Don't forget you can use https://devdocs.io/ too which also searches MDN and store offline. The two are a great pair.
No Elm there?
230+ sets of documentation already work. You can vote for your favorite language here: https://trello.com/b/6BmTulfx/devdocs-documentation
Re: Documenting the Web together
#140This news sounds great to me, but I feel like I don't understand what's happening behind the curtain and don't grasp the second-order consequences. What would motivate them? I wonder what the political motives are (industry politics, not the other kind that we won't mention here). Could this eventually displace standards bodies such as WHATWG and W3C? If the Product Advisory Board of Mozilla, Google, and Samsung agre…
In general I like that Google and others are doing this. The web is so complicated, so overwhelming, that a central source of documentation is needed. This "blog posts as documentation" culture is not healthy. However I think we should all be skeptical of any actions corporations take today until proven otherwise. When 60,000 Americans are dying of opiods per year (that's all the deaths in Vietnam per year) and drug…
> (who could of believed they would do that??)
I didn't even realize I was being cynical when I was unsurprised by this news. I don't really understand why everyone else is. (That isn't to say it isn't important news, but the shock that everyone seems to be in is confusing).