It looks like JAPH scripts are often misinterpreted for
obfuscation stuff, when often they are not.
Actually, I have downvoted several JAPH nodes for not being
"obfuscated enough" for me... Since I seldomly gave advice
on how to make those better (in my view), this led to bad
feelings/votes.
After a discussion in CB with kel and others,
we found that maybe the problem is elsewhere: JAPH and
obfuscation are actually different. Check this summary:
JAPH | Obfuscation |
|
- prints "Just Another Perl Hacker"
- discovery of features
- less used features used in unusual ways
- TIMTOWTDI
|
- does something useful/funnny/powerful
- hard to understand/read programs
- an artistic approach to the code
- should confuse B::Deparse
|
It looks like there is a need for a second section, dedicated to JAPH
writers. When they get used to those twisted ways of using
our beloved Perl, they can switch to Obfuscation...
-
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.
|