(Or, rather, that language alone doesn't guarantee success, but that would be too rational and boring for an online forum).
Just because computers obey the law of excluded middle does not mean we should.
For that to be true, more than a quarter would have to be in the bottom 25th percentile. (In fact, it still points to lisp being better than average).
Anyway, The bottom 25th percentile of the competition is relegated to submissions that didn't run.
There was a bug (still is, I believe) in the lisp 'starter pack,' which caused the client to crash (It sent garbage to the server or something). So even the default Java starter submission would beat it.
Given the number of people who submitted once and walked away, I wouldn't read too much into it anyway.
Of course the program could be rewritten into qbasic. It is getting your ideas and thoughts into a form that is not a compromise to the language which matters.
Given that people have argued that the absence of Lisp winners from such competitions is evidence against Lisp's greatness (I'm going by memory here and don't have time to dredge up the record), it seems relevant to point out when it does happen.
a) given that people has made bad arguments before b) it "seems relevant" to make bad arguments in the opposite direction now
Huh?
http://news.ycombinator.com/item?id=1961546
Obviously the OP is relevant for other, better reasons than this, but that's what my comment meant.
A: "Lisp sucks. If it didn't, we'd see it winning contests or something"
B: "But it has been used to win a contest. Besides, you're really bad at making an argument"
I'm not trying to disagree with the OP in general (you can't fight bad logic with more bad logic) but just pointing out that correcting someone's facts can be easier (and with this datum point, possible).
Edit: I like the upvote, but an explanation would be better.
From the article: "Lisp doesn’t get in my way as much as other languages."
Programming languages are like basketball shoes. You need a minimum feature set to play safely (ankle support, good traction, comfortable arches, etc). But buying a Nike Zoom Kobe will not make you the next Kobe Bryant. So what's the minimum feature set for a good programming language? I don't know. C appears to be good enough, while assembly is not.
That said, Kobe Bryant could probably beat me at basketball wearing a pair of cowboy boots. Likewise for programmer skill vs. task vs. language appropriateness.