It isn't an argument against
nextgen, it is an argument against defaults.
Why aren't they your cup of tea? would be the question that would permit me to make
nextgen better, unfortunately I didn't ask that. Instead, I brought to light the weak merits of arguing against defaults, and against a method that tried to better them.
And, not respecting one argument does not mean that I do not respect the opinions of others. I respect that he won't use my module because he prefers to replicate boiler plate code through editor macros (for some value of respect), that doesn't mean that the source argument against implicitly doing what you want is a good one, especially for the perl community.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.