Re:The evolution of the web, and a eulogy for XHTML2
by james-skemp on Sunday October 27, 2019 @10:12AM
(#21369785)
I wonder how many people think it was unreasonable due to how you had to send back the page to be truly valid; application/xhtml+xml, application/xml, or text/xml. Due to IIS, browser support, and the platforms I personally used, that was the only requirement I never felt I had to meet.
I personally agree with you, and still close my tags, use quotes around attribute values, and provide empty/duplicate values when needed.
I also still use XML for data storage, and used ColdFusion back in the 6/7 days, so that probably had a influence on my choices.
Re:The evolution of the web, and a eulogy for XHTML2
by jefftk on Sunday October 27, 2019 @08:32AM
(#21369313)
I agree the approach sounds reasonable, and I think if we were having this conversation twenty years ago I would have been on the pro-XHTML side. But we tried it, and it didn't work.
Re:The evolution of the web, and a eulogy for XHTML2
by pdimitar on Sunday October 27, 2019 @10:10AM
(#21369770)
Not sure I ever understood why it didn't work exactly. Do you have examples?
Re:The evolution of the web, and a eulogy for XHTML2
by Vinnl on Sunday October 27, 2019 @11:31AM
(#21370325)
People who did try to author XHTML often inadvertently introduced the yellow screen of death, and did not feel they were getting anything in return.
Re:The evolution of the web, and a eulogy for XHTML2
by mkozlows on Sunday October 27, 2019 @11:55AM
(#21370513)
Here's the classic Hixie write-up, from 2002: https://www.hixie.ch/advocacy/xhtml
Re:The evolution of the web, and a eulogy for XHTML2
by goto11 on Sunday October 27, 2019 @04:46PM
(#21372278)
XHTML could either be served as HTML or as XML. When served as XML it would not render in all browsers, but when served as HTML it would. Since serving as XML did not provide any particular value for the document author, there was no reason to use it. But XHTML served as HTML is just HTML with some extra slashes which are ignored.
Disagree. You open the tag, you close it. Nested. I worked with a non-developer who had some KML (https://developers.google.com/kml/) dumped on her without any training whatsoever and when I explained a few basic thing, including the above rule, she got the principle of it in a few minutes. Because it's not hard (although dumping a KML task on a non-dev is a bastard thing to do).
> but people weren't using XML editors
I personally think that lowering the bar to let as many people in as possible isn't necessarily a good idea. Just IMO