In addition to what roboticus said above, golfed solutions are often not what you would want to use as production code. Golf is like a workout for the mind. It keeps you in shape, but is not the real purpose (unless you make money by lifting large amounts of weight and putting it back down).

Golf solutions explore the corner regions of the language where few people explore. The creativity required to produce some of these solutions make them unacceptable for use in anything more than an exercise. When writing production code, you are writing:

• to codify an algorithm
• to effectively communicate that algorithm to future maintainers, including yourself

The second item, especially the effectively part, can be lost in the golfing process.