6 ms·

Good insights into voodoo problems. Slightly unsure about the sweary angle though, I love a swear up as much as the next man, but in this it feels unnecessary.

wubbfindel 13y ago
Agreed. It's a shame that swearing has to spoil a potentially good resource. I won't be able to share this will my little brother, who could benefit from this while learning to code, purely because of the amount of swearing.
- bloke_zero 13y ago
  Maybe, but it's hard not to forgive swearing in any piece mentioning ie6.
- caio1982 13y ago
  You guys are being too harsh on it. Or apparently I failed to see how one "wtf" in the title and one "fucked" in the header could spoil such good resource. I'm sure there are many ways to go around these two if you want to point it to your little brother.
- watwut 13y ago
  What amount of swearing? There is exactly one "wtf", exactly one "fuck" and the rest is polite. If you do not want to show it to brother, more power to you and you got my respect for thinking about what language he picks up. Really. However, the resource has exactly two impolite words in it, so it is hardly huge amount.
  - robobro 13y ago
    There's 2 "shit"s too. Maybe the author feels obliged to curse a little bit, and mostly in jest / for its own sake because the domain name includes a simulacrum of obscenity (WTF) in it.
  - wubbfindel 13y ago
    Fair comment, it's not a "huge" amount of swearing. But I didn't say that it was. It's just too strong for me to feel comfortable sharing it with younger ones. I guess a more accurate way to describe the issue for me would be to say it's because of the "strength" of the swearing rather than the quantity. However, I will be sharing this with co-workers! It's a good document for reference.
- deleted 13y ago
  [deleted]
- icantthinkofone 13y ago
  Swearing for the sake of swearing is never appropriate. I agree with you.
- rmrfrmrf 13y ago
  Wait, wait! Just fork the repo and send your brother an edited version!
- Aldo_MX 13y ago
  Ditching a resource just because a bit of swearing? You all can't be serious...
lumpypua 13y ago
Are you kidding?!? Do you know how much swearing solving voodoo html/css problems has caused? This is but a ghost of the blight of cuss they've brought on the world.
CmonDev 13y ago
Instead of fixes to fundamentals we get HTML5 feature creep. I think there should be way, way more swearing. An email should be sent to each member of WWWC each time this website is opened by someone.
tericho 13y ago
Submit a PR, Mark seems like a reasonable guy I'm sure he'll oblige. https://github.com/mdo/wtf-html-css/pulls https://github.com/mdo/wtf-html-css/pulls
- markdown 13y ago
  Reasonable? Isn't this the guy whose ego is so great he crapped all over Douglas Crockford when that man so generously spent time trying to help improve Twitter Bootstrap? The very same Douglas Crockford who has contributed so much to building the JS/frontend community to what it is today.
jessaustin 13y ago
Maybe there should be an Accept-Vulgarity http header, which some HN readers would keep set to "scatology;q=1.0, obscenity;q=0.9, banality;q=0.1"?

wubbfindel 13y ago

Agreed. It's a shame that swearing has to spoil a potentially good resource. I won't be able to share this will my little brother, who could benefit from this while learning to code, purely because of the amount of swearing.

bloke_zero 13y ago
Maybe, but it's hard not to forgive swearing in any piece mentioning ie6.
caio1982 13y ago
You guys are being too harsh on it. Or apparently I failed to see how one "wtf" in the title and one "fucked" in the header could spoil such good resource. I'm sure there are many ways to go around these two if you want to point it to your little brother.
watwut 13y ago
What amount of swearing? There is exactly one "wtf", exactly one "fuck" and the rest is polite. If you do not want to show it to brother, more power to you and you got my respect for thinking about what language he picks up. Really. However, the resource has exactly two impolite words in it, so it is hardly huge amount.
- robobro 13y ago
  There's 2 "shit"s too. Maybe the author feels obliged to curse a little bit, and mostly in jest / for its own sake because the domain name includes a simulacrum of obscenity (WTF) in it.
- wubbfindel 13y ago
  Fair comment, it's not a "huge" amount of swearing. But I didn't say that it was. It's just too strong for me to feel comfortable sharing it with younger ones. I guess a more accurate way to describe the issue for me would be to say it's because of the "strength" of the swearing rather than the quantity. However, I will be sharing this with co-workers! It's a good document for reference.
deleted 13y ago
[deleted]
icantthinkofone 13y ago
Swearing for the sake of swearing is never appropriate. I agree with you.
rmrfrmrf 13y ago
Wait, wait! Just fork the repo and send your brother an edited version!
Aldo_MX 13y ago
Ditching a resource just because a bit of swearing? You all can't be serious...

lumpypua 13y ago

Are you kidding?!? Do you know how much swearing solving voodoo html/css problems has caused? This is but a ghost of the blight of cuss they've brought on the world.

CmonDev 13y ago

Instead of fixes to fundamentals we get HTML5 feature creep. I think there should be way, way more swearing. An email should be sent to each member of WWWC each time this website is opened by someone.

tericho 13y ago

Submit a PR, Mark seems like a reasonable guy I'm sure he'll oblige. https://github.com/mdo/wtf-html-css/pulls https://github.com/mdo/wtf-html-css/pulls

markdown 13y ago
Reasonable? Isn't this the guy whose ego is so great he crapped all over Douglas Crockford when that man so generously spent time trying to help improve Twitter Bootstrap? The very same Douglas Crockford who has contributed so much to building the JS/frontend community to what it is today.

jessaustin 13y ago

Maybe there should be an Accept-Vulgarity http header, which some HN readers would keep set to "scatology;q=1.0, obscenity;q=0.9, banality;q=0.1"?