If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

People who liked Vectors since the beginning, had nothing else (to work on it), except VML and XML, because the actual SVG is nothing but a W3Cs re-branded VML. Meaning, when VML was around, - SVG didn't exist.

Regarding this, a reasonable question will rise: why didn't you use XML + VML at times when there was no other support of any sort of vector graphics except VML and when SVG didn't even exist?

On thing that XHTML has that I found HTML5 doesn't: custom character entity references!

I don't think it was probably used enough for people to care about it. The pros of HTML5 outweigh the pros of XHTML. Perhaps one of the biggest differences I can see between the two besides the tags and closing them with a "/" is that HTML5 seems to be trying to do away with styling attributes of tags. Which is a good thing, styling something with an attribute is bad for graceful degradation. It also removed some of the styling tags that are more for styling like the <center> tag.

Lol I agree with Justos. You know the great thing about HTML5 is that you can type your code exactly the same, like and image tag ending with a />. But it is no longer required. it can now be typed like this <img src="" >, also the declaration tag on top of the page is much easier to write. <!doctype html>. It's a pure pleasure to write it then those long over winded ones that did nothing. HTML5's header is the only one that does something.

The "Long-winded Doctypes" never bothered me in the slightest. Especially when I made custom ones for my own XML languages, and definately not when my own site is a hodgepodge of various versions of HTML (all the way from HTML 2.0 to XHTML 1.1, just for giggles).

The "Long-winded Doctypes" never bothered me in the slightest. Especially when I made custom ones for my own XML languages, and definately not when my own site is a hodgepodge of various versions of HTML (all the way from HTML 2.0 to XHTML 1.1, just for giggles).

Regardless of you wanting to stick to the past, HTML5 is going to be the way to go eventually. Browsers will drop support for others, although that probably happen for quite some time. So you don't really have anything to worry about.