Sorry you said not interested but I have to comment on this
> disagree that HTML has "failed" in almost any sense
The web was born in html, at some point web development skill shifted from it to mostly js. Why do you think that's the case if not html itself failing to accommodate for modern web development requirements?
It's not a joke that html isn't a real programming language. You can only go so far with it and it definitely offers zero help in modeling the problem's domain or any high level thinking process that programming encompasses.
Even so, web developers always had the option of sticking with an imperative approach to UI, like using element.innerHTML = '...', but overwhelmingly they preferred more declarative solutions like React. You could just as easily make the argument that the shortcomings of HTML had nothing to do with its "declarativeness", since that part was retained. I think a more likely explanation is that HTML couldn't be used to express the more complicated SPAs that people wanted to build, and regardless of what you think about those, JS-based solutions had to fill that need.
You and I can both claim opposite things without citation, but we both know which is closer to reality based on what skill is on demand in the job market and what's LOGICALLY required to make web apps with such and such capabilities.
> disagree that HTML has "failed" in almost any sense
The web was born in html, at some point web development skill shifted from it to mostly js. Why do you think that's the case if not html itself failing to accommodate for modern web development requirements?
It's not a joke that html isn't a real programming language. You can only go so far with it and it definitely offers zero help in modeling the problem's domain or any high level thinking process that programming encompasses.