On Sun, 19 Feb 2012 23:39:22 +0100, Kevin Wright
<[email protected]> wrote:
With XML/XHTML it gets worse. We not only ramp up the number of elements
demanded by ever-richer content, but also have the rule that each element
must be 'closed' so that we can maintain structural validity even whilst
manipulating those elements. It's an explosion of boilerplate in a
format
taken far outside of its original use-case.
I don't understand why so many people (not only Kevin) see XML as a
problem, while I see XHTML an improvement over HTML, and don't see tons of
boilerplate. But I understand the remainder of the points.
Sad but true... HTML is still a necessity for no other reason than tool
support. Even then, attempts to use HTML as a templating language have
often been less than successful; I'm sure we all remember how many
earlier
tools would just choke and die when encountering JSP's <% %> and other
such
non-standard tags from alternate frameworks.
Exactly. But what I meant was precisely templating by HTML tags, not
"quasi-HTML" tags. For instance, Wicket basically uses plain HTML.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
