Earlier quoted context omitted.
> accessibility is immediately out of the window, when it only renders a white page That's not the case for 99.9% of users. > if one allows its JS to run JS is enabled by default in every major browser. It's the _standard_, _typical_ way to browse the web. > The typical React app also will use some "components" thingy, instead of standard HTML form elements Components only exist in JS, not in the DOM. In DOM, they sh…
> Components only exist in JS, not in the DOM. In DOM, they show up as regular HTML input elements. That doesn't really deal with the consequences we experience at all. The mess is still created and 5-10 additional layers of nodes deep. The idea of making general use components, that "everyone can use in any situation" inside a JS framework, necessarily leads to this. The general purpose components handle cases, that…
https://github.com/hober/tangler/blob/main/index.html
Does this look like it was written by a person who has "vastly more expertise"? This was made by the Chair of HTML Working Group and President of ECMA. It's an awful, unreadable mess. How is that person supposed to lead and shape the future of the Web?
The myth that people at W3C and ECMA are somehow god-tier engineers and designers is just not true at all and it's been proven many, many times. They are completely disconnected from reality and don't build modern apps at all, how are they supposed to know how to do it well? It's why we have TypeScript, why SASS/SCSS was popular, why we need component libraries to add basic fucking features to HTML or why half of browser APIs are abstracted away into JavaScript libraries by people who got frustrated one too many times.
> already cover almost every use-case one can think of
They literally don't, if they did we wouldn't have to build extra stuff on top - no one wants to do all this abstraction work, but there isn't any other way.
If you wanted to build a stupid autocomplete dropdown in native HTML, you literally just can't. You HAVE to use JavaScript. This is a pattern used on MANY websites today, understood and liked by users and it's still impossible to implement natively.
Also competing business interests from Apple, Google and Mozilla make it so even if something IS a standard, it's not actually implemented the same way in all browsers or is not implemented at all.