Hacker News new | comments | show | ask | jobs | submit login

People keep telling me to use MDN but I find their sites bloated when I just want to quickly look something up (which is most often the case).

Random examples:

http://www.w3schools.com/cssref/sel_before.asp vs https://developer.mozilla.org/en-US/docs/Web/CSS/::before

http://www.w3schools.com/cssref/pr_background-repeat.asp vs https://developer.mozilla.org/en-US/docs/Web/CSS/background-...

I try to use MDN as often as I can; however, MDN often obscures the immediately useful information under copious amounts of text while W3 schools usually offers a quick use case that pretty much covers it.

eg. https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/S... vs. http://www.w3schools.com/html/html5_webstorage.asp

Also, if I don't get there by google search, I have a really hard time following a tangential thread through MDN.

I usually just open both resources—and often a third related blog post or SO question—and whichever one helps the best, I use.

Yeah, that's my thing. Within 0.2s, I get the w3schools result . It's the first one in google so I click it automatically.

I've tried using other resources but I hate this whole "let me show you most of the site in 0.2s, anddddd let me load everything else for another 3" just to look pretty.

Slightly offtopic, but when would you want to use a :before ?

It looks something out of CSS:the bad parts,ie looks very hacky but apparently is standard.

If for some design reason you wanted to add curly quotes around all links “” or perhaps display an attribute of the link as a hover-able tooltip, it would be better to use pseudo elements rather than adding content for the sake of the design.

Things that are subject to change and attributed to design choices rather than content choices are much easier to add and remove via `:before` or `:after` vs. going through the code and adding or removing elements.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact