Several reasons come to mind:
The current sections are laid out according to the type of petition or contribution you wish to make, not the functionality you're implementing.
We already have a large number of sections, a few of which can be confusing. Some have asked, for example, about the difference between Craft and CUFP.
The original intent is easy to understand, once you take time to ponder the Guide.
Style is separate from substance. By this I mean that good programming style applies to all programs, not just CGI scripts. Futhermore, there are many discussions in the archives covering stylistic issues. (I'll leave finding them as an exercise. Hint: Try starting here.)
Also, good HTML style is a slightly different question than good Perl style, one that can generate a lot of heat, smoke, and volatility.
For example, there are those who believe that you should never use anything more than simple markup. Others say that it's possible to use graphics, tables, frames, etc. very effectively. There are many opinions and ideas, but few hard and fast rules.
Given the reluctance some monks have expressed with blatantly off-topic discussions, you can see why there would some resistance.
Remember, Perl is more than a CGI scripting language; that just happens to be one thing it does well (provided, of course, you use CGI.pm;). Perl does many more things and, it's fine to use it as a CGI scripting tool. However, it can do much, much more.
--f
In reply to Re: new CGI/HTML section
by footpad
in thread Possibility of a new CGI/HTML section dealing w/ code style and asthetics
by bladx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |