4 ms·
> XHTML died because it was too hard for people to get stuff done. This is not true. The reason it died was because Internet Explorer 6 didn’t support it, and
by JimDabell 1y ago
> XHTML died because it was too hard for people to get stuff done.
This is not true. The reason it died was because Internet Explorer 6 didn’t support it, and that hung around for about a decade and a half. There was no way for XHTML to succeed given that situation.
The syntax errors that cause XHTML to stop parsing also cause JSX to stop parsing. If this kind of thing really were a problem, it would have killed React.
People can deal with strict syntax. They can manage it with JSX, they can manage it with JSON, they can manage it with JavaScript, they can manage it with every back-end language like Python, PHP, Ruby, etc. The idea that people see XHTML being parsed strictly and give up has never had any truth to it.
- troupo 1y ago> The syntax errors that cause XHTML to stop parsing also cause JSX to stop parsing. If this kind of thing really were a problem, it would have killed React. JSX is processed during the build step, XHTML is processed at runtime, by the browser.
- throw_await 1y agoInvalid XHTML woild have been caught in the test suite
- troupo 1y agoNeither you nor the sibling commentator can be serious.
- naasking 1y agoYes, which presumably would have actually been tested by someone before it was uploaded.
- troupo 1y agoNeither you nor the sibling commentator can be serious.
- naasking 1y agoHey, guess what else is processed at runtime: all of the dynamically typed programming languages that run half of the internet. I wonder how they can still get reliability despite that?
- troupo 1y ago1. They don't really 2. That is literally besides the point we're arguing here. At this point i have no interest in this "discussion". Adieu.