[Fucking stupid] Bad programming ideas [WTF]

Here's a thread where you can post retarded software/programming related ideas you read or saw on the internets. Retarded code from ENTERPRISE is fine too, but please don't turn this into “Retards writing Java” thread. You can think of it as /prog/'s own DailyWTF, only with less Java programmers and people laughing at stuff that they really don't understand. I'll start with a post from /a/:

I have been thinking about a P2P client which requests bytes from people who may not necessarily have the file they're downloading, but they have those specific bytes (which may be from another file), and the P2P client is designed to request the closed peer with those bytes, despite not having the file. So, it wouldn't matter if a torrent was dead, you'd just have to search other peers for those specific bytes.

It would have to be some sort of index of hashes of those bytes which would determine who sent them...

>>40
Processing power is growing exponentially; soon we will be able to rebuild files based on its MD5 hashes and their size.
No, we wont. You can't use a 128-bit hash to completely characterize an input of arbitrary length. For a input of length n bits, you'd have 2ⁿ - 2¹²⁸ hash collisions. Assuming an equally distributed hash, that means
2ⁿ - 2¹²⁸
-----------
    n
of the collision-causing inputs would be of length n. For any n > 128, this works out to a really fucking big number.

In other words, even if you had the computing power to enumerate all the files that hash to a particular value, you'd still have the problem of choosing the real original file among many plausible candidates, despite the fact that its length is known.

HIBT?