What is wrong with codecrap.com?
Nothing in particular, except it does not have a clear mission. The headline only reads
Where developers go to laugh and cry.
and that can mean many things. But I know one thing: It is incompatible with Code Review, we don't come here to laugh or cry, we come here to make ourselves and others better. People coming to Code Review know that there's something wrong with their code and come here to find out what. I have yet to see a user who did not appreciate the help and tips we gave 'em and wasn't willing to learn. On CodeCrap.com, it's not clear what purpose the site serves at all.
We do not even know who owns that site as the domain was registered via a proxy company.
Why posting code from Code Review on CodeCrap.com or similar sites puts you between a rock and a hard place.
The license for taking anything from Code Review is CC-BY-SA, so you're required to add a link back to the Code Review question. That way you open up the code and the OP for an out of context forming of an opinion. Is this bad? Not necessarily, but someone who does not know Stack Exchange might be tempted to do something stupid, like making an account and leaving stupid comments or downvoting the original question or reposting the code somewhere else without following the license.
Additionally only posting the code and removing all of OP's statements about their own code does not help in any way, as it leaves the code completely without context. The OP is aware that the code is not good, only posting the code removes that important statement completely.
We do not know the license of CodeCrap.com.
This is a minor problem, though. There's not a single license statement on CodeCrap.com, nothing that tells us what license these code samples are under. But it's propagated on Twitter and Facebook, and it' not guaranteed that the license of the posted content will be followed.
Code posted on Code Review is not crap per se.
Calling code that has been posted on Code Review "crap" is...not fair to say the least. The code might be crap, but calling it that (and only that) in the aspect that the coder came here to correct exactly that is not fair at best. We all wrote such code at some point, the important point is that we moved past it and now write better code.
We did not come here to say "that code is crap", but to say "that code is crap, but let me show you why and how to do better".