Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Documenting the Web together

blogs.windows.com

Post reply on HN
Print view View original

91–100 of 212 posts

Re: Documenting the Web together

#91

Post by dmitriid »

jsmthrowaway wrote: post #52
dmitriid wrote: post #44

Earlier quoted context omitted.

Apple never hosted web-related docs, so they probably don’t care.

Sorry, that is not true. Apple documents all of its platforms quite thoroughly, and Safari is one of them. Theirs is simply not an analogue to MDN. https://developer.apple.com/library/content/documentation/Ap... “Apple doesn’t attempt to document general-purpose Web technologies without an eye on its own platforms” might be a more accurate statement, but even that is shaky because they spent a lot of time explaining…

Ah. Missed that. Yup. It would be nice to see Apple's support behind MDN as well.

Re: Documenting the Web together

#92

Post by soapdog »

rainbowmverse wrote: post #24

For the people who have and will comment on how bad w3schools is, Google provides a Chrome extension for blocking domains in search results. https://googleblog.blogspot.com/2011/02/new-chrome-extension... I don't know if there's a Firefox version.

There is https://addons.mozilla.org/en-US/firefox/addon/hide-w3school...

Re: Documenting the Web together

#93

Post by iMerNibor »

y4mi wrote: post #81
fyrstenberg wrote: post #30

Don't forget you can use https://devdocs.io/ too which also searches MDN and store offline. The two are a great pair.

cool, i didn't know that site. wonderful ux how's the content added though? its missing so many libraries i use...

Seems to be scraping public documentation pages

https://github.com/Thibaut/devdocs/#scraper

Re: Documenting the Web together

#95

Post by schnevets »

Egidius wrote: post #14

For me, as an experienced front-end-focussed developer, MDN has been my go-to website for quick spec references. MDN has all I need to know, and I know my way around. However, I've been in teams where the less-experienced developers went to W3C Schools to see how they should implement some feature. And to be honest, I cannot completely blame them. W3C Schools shows directly what you need to know and how the API you a…

W3Schools tends to have a usable piece of example code at the very top of the page, while MDN gives an introduction and broader idea. Compare the display property page at the top of W3Schools vs MDN: W3Schools: https://www.w3schools.com/css/css_display_visibility.asp MDN: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/d...

Combine this and the higher Google rankings (My usual front-end searches display W3Schools, then StackOverflow, then sometimes JQuery or another library, then MDN), and you can understand where the problem lies.

Re: Documenting the Web together

#96

Post by _puk »

kbumsik wrote: post #7

The 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.

Sorry, I don't understand the overriding sentiment here..

Are we now asking Google et al to be the gatekeepers of what is deemed correct and useful because they have a preferred alternative that fits with our view on the world?

W3Schools may not have the best historic reputation, but it still has a place in relevant search results.

I have personally used MDN extensively over the years, and love it for what it is.

Re: Documenting the Web together

#97

Post by JTenerife »

amq wrote: post #16

Somehow I had more luck with stackoverflow and others when looking for a quick hint/example.

Yes, for hints like "how do I", but for JS ref like "methods on a Set" I use it all the time. Problem with SO is that often the anwsers are quite old (<=ES5).

Re: Documenting the Web together

#100

Post by roblabla »

shmerl wrote: post #76

> 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. That's a good move by MS. In this context it's great to see them supporting open codecs, and for istance OGG contai…

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.
Post reply on HN