This will be a very harsh post.

Are we Meditations sick? Are we Craft sick? How about Snippets sick?

I think I didn't express myself well. I thought of that golfing is a bad kind of premature optimization that we should avoid. If I see much code like that, I start to become like that without even noticing.

I mean, from most obfus, it is evident that you should not use such features in production code, still you can learn something from obfus, or ignore them. The difference with obfus is that they may seem like a good idea, just like most premature optimizations at first glance. While you may still learn from a golf, I think that putting them to the obfu section might help.

Also, how on earth is a golf challenge a valid SOPW?

You're right, it's not. Still some people have posted golfs there. (Some real golfs too, but some are only golf-like, the most often being to write the intersection of two regexen as one regex as short as possible: golf this reg ex) They probably don't understand why golf is bad. But a separate section would just make it worse.

In reply to Re: Re: Re: Golf Channel by ambrus
in thread Golf Channel by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.