6 ms·
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 w
by 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 agoMaybe, but it's hard not to forgive swearing in any piece mentioning ie6.
- caio1982 13y agoYou 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 agoWhat 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 agoThere'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 agoFair 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 agoSwearing for the sake of swearing is never appropriate. I agree with you.
- rmrfrmrf 13y agoWait, wait! Just fork the repo and send your brother an edited version!
- Aldo_MX 13y agoDitching a resource just because a bit of swearing? You all can't be serious...