Brainfuck., Boolfuck and Brainfork...

Till today I didn't know that following are real language. I heard these words from experts.....thought Ummm nice synonyms....but in reality
There is a complete wikipedia about this....

The brainfuck language is an esoteric programming language created by Urban Müller in 1993 noted for its extreme minimalism. It was designed to challenge and amuse programmers, and is not suitable for practical use. Its name has been variously bowdlerized, as in brainf*ck or brainfsck, since its name contains the expletive "fuck". The name of the language is generally not capitalized, despite the fact that it is a proper noun.

This language, Boolfuck, is based off of the programming language Brainfuck, for which it is very difficult to write useful programs. There are very few differences between this language and Brainfuck; the primary difference is that Boolfuck works with bits instead of bytes.

Brainfork was conceived during a german lesson in High School. As the teacher spoke his words of wisdom for hours on, the brains of the architects behind the language was beginning to slowly wear down to a state where only fundamental thought routines could persist. But then, all of a sudden, lightning struck. The beautiful Brainfuck language was thus extended to include yet another instruction: fork

There is a complete list of implementation...programms and other's...

Interesting isn't !!!!!!

Things to Say When You're Losing a Technical Argument...

Mr. Bad and Crackmonkey collaborate on a fine Mr. Bad's List
I believe I've hearing most of them - following are the great and get use to of listening them

1. I agree that it works in practice, but does it work in "_theory_" ?
2. I had the same thought ?... Ugh, I hate that one.
3. Yes, well, that's just not the way things work in the real world.
   
4. I like your idea. Why don't you write up a document and we'll review it at the next meeting?
   
5. That won't scale.
6. I think you need to stop taking this so personally. We need to think about what's best for the project, not about our own little pet theories.
7. Have you LOOKED at the number of I/O requests that will create?