There are no tools to embrace them, there is no way to make an universal web component like you can do with a React component without severely limiting what you can do and how you can develop it and how it performs. It's very sad, I'd love to use native Web Components but it's so bad it hurts (or you end up reimplementing incompatible React).

You're not understanding what web components are.

They alone are not a replacement for the entirety of frameworks, they are low level hooks that standardize the more fundamental level of frameworks: component instantiation, component lifecycle, and style and DOM encapsulation.

Higher level features like DOM rendering are left to libraries, and there are some really good libraries for that. And I'm not sure what you even mean by the libraries limiting what you can do how you can develop. There's way more choice in the web components ecosystem than within any single framework.

I think the biggest difference is that I consider DOM rendering a low level feature that should be abstracted away lowest as possible.

Yep, again the anti-WebComponents message.

Angular, Vue, Polymer, Svelte and a couple of Web based RAD editors look like tooling to embrace them to me.

Since I don't have any plans to ever use React, how does your magical component work with my tooling?

My component is "magical" thanks to the React ecosystem and because it uses the tools the React platform provides to greatly integrate with said ecosystem. The tools you suggested are not comparable to React - React Hooks and Contexts are the part I'm most interested in.

If you use different tooling, then it doesn't work, and that's okay. You don't need to care about React and I don't need to care about Web Components. It was suggested that React is useless and should be replaced with Web Components, and I'm simply saying that Web Components are not sufficient to replace React, not that you should switch.

Naturally my tools are not comparable to React, because by targeting WebComponents they support everyone on the browser instead of the React developers silo.

And best of all, they are even usable from React.