On 19 May 2008, at 11:24, Rimantas L. wrote:
produce/manipulate your code.
Well, some of our applications are scraped by other (desktop)
applications. Those applications benefit from the XML notation, since
they can just run the webpage through the XML parser and run over the
nodes they need. These are older apps, that either don’t have an REST-
based API in place or where the third party development team had no
experience with WebServices (they exist, believe me).
I myself prefer HTML 4.01 Strict - it is as strict as xhtml and does
rely on any bugs. True, HTML has more flexible syntax if you ever
(e.g. to shave off a couple of bytes), but you are still free to
close all your
LIs and Ps.
I don’t care how a browser interprets it tbh, I know not sending it
with the correct headers makes browsers interpret it just like HTML. I
prefer having the doctype keep me (and our development team) in line.
We’re protecting ourselves against… well… ourselves actually. We
all know the problems that arise in a team about how to name
variables. How to name variables: titleCase or under_scored or …
Using XHTML forces the team to adhere to the conventions, there is no
choice. It keeps the views pretty uniform, no matter who implemented
That said, everyone nowadays can basically use whatever they prefer. A
real choice will only have to be made when HTML5 and XHTML2 are
finalized and implemented in all browsers, since they are focussing on
totally different issues.
The fact that Rails defaults to XHTML would not bother me much if
was an easy way to configure it to use HTML mode, alas…
There is, use the plugin I posted in an earlier message and everything
is HTML4 compliant, unless I’m missing something?
Peter De Berdt