From: "Tony Ingenoso" 

This is a multi-part message in MIME format.

------=_NextPart_000_003C_01C39781.10D9A420
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Just because some broken retarded "feature" has been officially
codified = doesn't mean it should be used by mainstream apps.  Broken and
retarded = aren't negative traits that are magically rehabilitated by
codification. =
 A turd with the UL seal of approval on it is still a turd.

The app writers should use a bit of common sense and say to themselves, =
"gee, this is a real grody kind a thing, lets stay away from
this". =20
  "Rich"  wrote in message news:3f8e339a{at}w3.nls.net...
     Believe what you wish but this mechanism is codifiled in the HTML =
standard.  Comments allow for constructs that are to be ignored by =
implementations that don't support them.  If you think that backward =
compatibility is stupid, so be it.

  Rich

------=_NextPart_000_003C_01C39781.10D9A420
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








Just because some broken retarded =
"feature" has=20
been officially codified doesn't mean it should be used by mainstream=20
apps.  Broken and retarded aren't negative traits that are =
magically=20
rehabilitated by codification.  A turd with the UL seal of
approval = on it=20
is still a turd.
 
The app writers should use a bit of =
common sense=20
and say to themselves, "gee, this is a real grody kind a thing, lets =
stay away=20
from this".  

  "Rich" <{at}> wrote in message news:3f8e339a{at}w3.nls.net...
     Believe
what you wish =
but this=20
  mechanism is codifiled in the HTML standard.  Comments =
allow for=20
  constructs that are to be ignored by implementations that don't =
support=20
  them.  If you think that backward compatibility is stupid, so be=20
  it.
   
  Rich
   

------=_NextPart_000_003C_01C39781.10D9A420--

--- BBBS/NT v4.01 Flag-5