Comment by JimDabell
1 day 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.
> 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.
Invalid XHTML woild have been caught in the test suite
Neither you nor the sibling commentator can be serious.
Yes, which presumably would have actually been tested by someone before it was uploaded.
Neither you nor the sibling commentator can be serious.
1 reply →