In the "Who is Responsible" section on the WhiteSpace link:
The interpreter was written by someone who shouldn't have stayed up so late, Edwin Brady, and the language was designed by two people who shouldn't have had so much to drink, Edwin Brady and Chris Morris. No doubt Andrew Stribblehill isn't entirely blameless either. ....
In a brainf*ck wiki article, they state:
Many people at various times have tried to extend brainf*ck to make it easier to program in, but such efforts have been compared to trying to make a luxury car by gluing parts onto a skateboard. Other people have been interested in variations of the language for theoretical purposes, pedagogical applications, etc. ...
Don't forget MUMPS!
oooh great buddy , yes i will check this link :) to know about it :)
Hey, sorry buddy, but I think you missed that this thread has rapidly turned into a joke. Whitespace, BrainF*ck, MUMPS, and a couple others mentioned are languages you probably never want to learn for any reason unless you're a masochist. Good luck, my own ++ for java - still the most prevalent language out there (I'm a java dev who also does Groovy on Grails and Ruby on Rails)
Isn't one of the "selling points" of whitespace that it's really secure?
All you have to do is print out the code, delete the file on your system, and you have a hardcopy that no one will be able to read!
Hahaha. Personally, I do all my whitespace programming in ebook format. I search and replace all the spaces in a classic novel with my code. Very useful, other than the odd word spacing :P
Is it wrong that I'm now sat here thinking "that might just work"?
It has been done actually. If you put all your whitespace code in the larger white areas, like at the end of lines and in between paragraphs, the whitespace parser treats all printable non white characters as comments - just ignored. You could probably imbed a substantial program into a large ebook :D