Comments on: Semantic code = coding usability

By: len

len — Fri, 22 Apr 2005 06:04:00 +0000

We should definitely NOT use XHTML as tagsoup.
Stick to simple and semantic code, whatever you plan to use, HTML or XHTML.

By: Len

Len — Thu, 21 Apr 2005 06:04:07 +0000

I know what you mean, but people will not understand if you talk about HTML.
Cause isn’t that what they all did the last 5 years?
Promoting HTML, but calling it XHTML is not a bad thing (that is what I’m doing).
Most website are not even ready for the basics: semantic HTML code.
So XHTML and making adjustments to server settings is the right thing to do, but probably not possible in the near future.

COMMENT:
I’m actually advocating HTML. (And with that I don’t mean tag soup.)

By: Bj�rn Seibert

Bj�rn Seibert — Wed, 30 Nov -0001 00:00:00 +0000

Yes, the coding practice IS the main reason for using XHTML (as tagsoup). People write propper code, throw unnecessary elements out of the window and think about using semantically relevant elements. So I think too, theres no harm to a website, when using XHTML as tagsoup.

By: Douglas Clifton

Douglas Clifton — Wed, 30 Nov -0001 00:00:00 +0000

I couldn’t agree more, well said. There are so many purists out there that claim you shouldn’t use XHTML at all unless every browser starts suddenly supporting it. In my mind the goal is to advocate clean markup by using it now, and the more people follow suit, the sooner the Web will start improving. There are ungodly amounts of bad sites out there, and it is my belief this stems entirely from browsers that are designed to allow laziness on the part of developers.