3 ms·
Let's build a website using XML
- Alifatisk 3y ago> One of the reasons XML (and XHTML) fell out of favour is that they are unforgiving. Miss a /? Your site is broken. Forget to close an element? Your site is broken. Incorrectly escape something? Your site is broken. Mismatched elements? Your site is broken. Isn't unforgiving and being strict a good thing?
- edent 3y agoWhat's the user need for strictness? HTML won over XHTML because users never saw a cryptic error message. Users can't fix broken XML - neither can browsers. HTML is a better experience.
- devdude1337 3y agoBack in 2013 we built a software with xulrunner and extensive usage of XSL/T. It allowed us to create an absurdly complex UI with precise rendering. No CSS. Despite the lack of animations -that we have in CSS - it was superior for custom UIs. Today you could argue, that we need to be specific about closing tags properly again when using something like JSX so it gets cough compiled. XSL/T is tedious to work with, but it’s also strict and easier to debug than to push pixels with CSS. Honestly, I don’t know why we left that path, but I feel dropping XHTML may not have been a decision made by software engineers…