commenting code (was Re: [thelist] Tip)

April april at
Thu Feb 15 16:31:19 CST 2001

1.  If the presence of a comments is enough to noticeably affect page
renders times on someone's computer, and you care about that someone, you
shouldn't be having tables on the page either.

2.  Comment how you please.  They're comments.  If someone else is going to
look at your source and be offended... they have looked your source and been
offended.  If you don't care, it doesn't matter, and if it was a business
site I hope you had the sense not to do it in the first place.

----- Original Message -----
From: "Scott Dexter" <sgd at>
To: <thelist at>
Sent: Thursday, February 15, 2001 3:40 PM
Subject: RE: commenting code (was Re: [thelist] Tip)

> > PS Maybe you don't want to do this on a corporate site, but I
> > personally like the way sites like are
> > commented, with curses at Netscape and so forth.
> I would suggest not commenting like that at all. An example,
> "<!-- Thus endeth the branding. Begin content. The following table
> the rest of the page. May our readers do likewise. -->"
> *puke*
> Couple things:
> 1) verbosity == file size == page load. Comments are good, but c'mon
> make them to the point, as they affect how quickly the browser can render
> the page. This includes server side comments as well (ASP, CF). The
> client/server parsing engine has to parse comments and code alike. Don't
> nuts with verbosity
> 2) How much self-love (putting it nicely) can we take?! Who gives a rat's
> ass what they would like the reader to do?
> As far as I'm concerned, the above example should be
> <!--     BEGIN CONTENT     -->
> and f*ing end it at that.
> sheesh.
> sgd
> ---------------------------------------
> For unsubscribe and other options, including
> the Tip Harvester and archive of TheList go to:
> Workers of the Web, evolt !

More information about the thelist mailing list