You can't just say "React" though, you have to show how it actually integrates with the DOM that we have. "Throw away the DOM we have" isn't a realistic option either.
How is React different from any of the libs and frameworks you are supposed to use for WebComponents? [1]
As for the API. How about a declarative API lime the one Polymer uses? [2]
[1] https://twitter.com/dmitriid/status/987771666846699520?s=20
[2] https://twitter.com/dmitriid/status/865518972380237825?s=20
I mean it’s decidedly not React to be clear, but I’m not sure what makes it atrocious
And that's just two attributes.
This doesn't make the API any less atrocious. And it would be nice if the platform didn't rely on libraries to make it usable.
"Nice" APIs or higher level APIs are desirable of course, but they tend to be much bigger in size and scope, much more opinionated and brittle than a smaller low level API. A portable API which browser makers can accurately implement and support for the long term, is a smarter goal even if it does expect devs to build a "nice" layer on top of it first.
As it stands now, it's nigh unusable by developers. Almost no frameworks even use it as their foundation. And those that do compile to them go out of their way to never ever use it anywhere except in base classes, maybe: [2]
As a result, today, 9 years (!!!) after they were first proposed, the very person who proposed them relegates them to "webcomponents will be used incidentally not totally" [3]
[1] https://twitter.com/dmitriid/status/865518972380237825?s=20
[2] Stencil compilation: https://twitter.com/dmitriid/status/1283445578853158917
[3] https://twitter.com/slightlylate/status/1283053719563563008