This question already has an answer here:
I was reading a question on Meta discussing how this site fits into the mission of Stack Exchange. A lot of the answers and comments all point to the same thing, that this site gives us a chance to look into different possible ways of problem solving in our favorite languages.
The problem is, this site has become dominated by code-golfs. On it's own, that's not really a problem. The problem is that there are languages specifically designed for that purpose that don't really serve purposes in the outside world.
I've seen very, very interesting methods of solving a problem written in C or Java or Python that were buried under a pile of CJam and GolfScript solutions that were 20-50 bytes long. They all use the same algorithm, but have their own clever ways in their language of solving the problem.
I'm not saying that golfs or golf languages are bad. I Think that there are many good examples of them. I also think that there are many interesting algorithm type questions that don't get answered in many languages because they are a golf. They are not won by coming up with a unique algorithm but by how little code you can write.
I'm trying to see if people are open to reconsidering the code-golf criteria for something more algorithmic or the like. Basically, consider if the best scoring model is shortest code instead of most efficient algorithm, most creative use of language, etc.