The phrase "crappy code" is subjective and not easily measured.

What you consider "crap" may be pure art to the people that produced it. Perhaps you just lack their perspective? Perhaps you've never had to write code in that language or at that scale? Perhaps they are just learning to code?

The world is bigger than individuals. Some code may be "crap" to you, but let me assure you that your code is "crap" to someone else.

Linux kernel code is often called "crap" by the OpenBSD developers. In their mind it is. I'm sure Linux kernel devs feel otherwise and in places where they aren't proud of it, they slowly improve it to make it better. Oh, and BTW, the "crap" that is the Linux kernel supports far more hardware than OpenBSD will ever support.

So in my mind, it's all a matter of perspective and goals. Nothing is "crap". And calling it "crap" is wrong and may cause others to feel bad about themselves and their project. It's juvenile and unnecessary.

If you are interested in the project and think it's "crap" do something constructive, submit your glorious code to make it better and to enlighten us all.

I was referring to what the parent called 'horrible code'. There's definitely a little of both: some of it cannot be measured, some of it can. Code performance is easily measurable for instance. Code size and simplicity can also be roughly measured.