💾 Archived View for station.martinrue.com › krixano › 8d6e6739d8a04a0f9be678d51a487006 captured on 2024-02-05 at 11:50:46. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-08)
-=-=-=-=-=-=-
So, apparently, after XHTML 1.1, the W3C tried to move towards XHTML 2, but a new web standards group (WHATWG) worked on HTML5, so W3C ended up accepting HTML5. Now it seems they are trying to work on HTML5 and XHTML5 in parallel. What's interesting is the benefits of XHTML, the ability to use XML namespaces for combining different XML "formats" in one XML document, seems to be becomming a bit redundant since the addition of web components and custom elements (which ends up making HTML5 more extensible), as well as the ability to embed SVG and MathML. However, web components I think needs JS. Idk, feels like a bit of a mess, and a bit redundant, imo.
2 years ago · 👍 mfoo2
XHTML is a tech bro fantasy. if only people would write their websites like a perfect valid parse tree, the web and life would be better, man. Life had better things to do with its time. HTML5 got it right. · 2 years ago
@astromech Yeah, I started getting into HTML (and later programming) when XHTML 1.1 was a thing, so it was the first one that I learned, I believe, although probably not well-formed XHTML (since from reading about it, you weren't supposed to send XHTML as text/html, and IE9 or IE10 was the first version to actually support XHTML). In 2008 I would have been 10 years old, which is about when I started programming (I remember using Visual Studio 2008 at some point - mostly Visual Basic, lol). I would have been doing HTML prior to that age then (at least age 9, maybe 8). · 2 years ago
I recall the XHTML days... Good times. · 2 years ago
WHATWG (Apple, Google, Mozilla, Microsoft) :vomit: · 2 years ago