The following is an attempt to stomp out the seemingly endless FUD that circulates about Web Components, most of which is purely manufactured by attacking tangential, opinionated choices of frameworks that happen to use Web Components in a way that differs from the opinions of other frameworks.
Don’t let me catch you claiming a Web Component is anything but the following, or I’ll send Kam Chancellor to lay you out:
Web Components are an amalgam of APIs from two W3C specs (Custom Elements and Shadow DOM) that enable the creation of encapsulated, declarative, custom elements, which serve as standard, reusable, interoperable vehicles of discrete, stateless functionality.
Myth 1: “Web Components are at odds with Framework X”
This is probably the most fallacious statement about Web Components.