Greetings,
warmly seconded.
I have often been more radical in my head on this one, but I will now step out of the closet, and let the flames burn who they may.
I think that the race to obfuscation, as fun as it may appear, is ultimately harmful for a programming language (be it perl, C or anything), and for several reasons.
- It is bad PR to begin with: "ah, XX, the language that has obfuscation contests, blah, blah"
.
- It promotes the extremely damaging idea that cryptic coding is cool programming
.
- In general, it suffers from all the handicaps of any virtuoso performance: a virtuoso violinist is able to play Bach's Chaconne on one leg using a shoestring as a bow, however, the Chaconne is played badly and at the end you still know nothing about his violinist skills.
This discounts the fact that one person's cryptic code may be another persons idea of clarity...
Cheers,
alf
You can't have everything: where would you put it?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
