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...
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, 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, 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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
