In the past decade (2010), developers at Google drafted the first specs of what we know as Web Components. But since then, there were back and forth discussions about how to implement them, and popular frameworks like React, Angular and Vue were created or revamped. Today, we have a stable set of tools supported by most evergreen browsers that could make us think again about using Web Components in our projects.

But, shall we use them? And if yes, will they work with my framework/library of choice, or do I have to rewrite my entire site? In this talk, we are going to answer these questions and try to provide a clear idea of what Web Components are and what they are for.

The goal of the talk is twofold.

First, introduce what web components are and what they are for, which is useful for newcomers, and then move to real use cases where this technology shines. We will point to the specs to allow people to continue digging into them after the talk.

Then, we will compare mainstream libraries/frameworks like React, Angular and Vue with Web Components to clearly identify when they are solving the same problem and when they are not. And how they can play together if needed. This second goal focuses on explaining that we, as developers, should use the right tool for the job.

The key message of the talk is: don’t go around chasing new trends, use what solves your needs. And, if you really need to use something new, you can do it progressively.