DrScriptt

It turns out that I’ve mostly been writing #XHTML when I thought I was writing #HTML for the past 25 years.

I was never cognizant of the fact that it was closer to XHTML than HTML.

But that does help explain why I thought that the HTML that I’ve been writing was so close to #XML.

🤔💡😁

Mar 20 at 6:46amWeb
Show threadJens Oliver Meiert2d ago

@drscriptt, my favorite topic 🙂

You mean, pardon the link, writing it fully like this, https://meiert.com/blog/write-html/#toc-the-xhtml-way?

Write HTML, the HTML Way (Not the XHTML Way) · Jens Oliver Meiert

You may not use XHTML (anymore), but when you write HTML, you may be more influenced by XHTML than you think. You are very likely writing HTML, the XHTML way.

Show threadDrScriptt2d ago

@j9t interesting read.

I’m not seeing any problems with writing #HTML the #XHTML way.

I don’t mind the rules or extra bytes.

I’m also doing more with #XML proper and #XSLT.

So consistent habits / style of writing HTML like XHTML doesn’t seem like a negative to me.

Plus it means that I can apply XML methodologies to my (X)HTML.

I fully acknowledge that people working on HTML and not any XML would probably benefit from HTML as HTML. But I’m not in that camp.

Show threadVivien (dentelle & numérique)2d ago
@drscriptt I regularly see people brandishing the previous-millenium-era broken markup as modern html and I don’t fully understand why. It’s so easy to close the elements in the correct order, or add a slash at the end of an empty element. It turns something only a web browser can correctly parse into an interoperable and extensible document.