None of these HTML-based technologies ever really replaces the others, but certainly web components make some use cases easier than React -- and make quite a few things possible that would be nearly impossible in React.<p>The best example right now is the new Photoshop for the web, which runs entirely in the browser and is made with web components and Lit. Fighting the "React way" to build something like PS would be a nightmare. But web components are a blank slate. You don't have to fight anything; you do have to built it the way you want it to work.<p>The extra building work includes ugly plumbing stuff like routing and state management, but the advantage is that you get to build those the way you want them to work, too.<p>In the cases where you're building an app with off-the-shelf kind of UI components and behaviors, a framework like React or Angular is still a good bet. Web components (and Lit, their "helper glue") lets every component be entirely custom.<p>I wrote an intro[0] to web components on Medium that's been well received if anyone is interested.<p>[0] <a href="https://medium.com/gitconnected/getting-started-with-web-components-lit-part-1-911aa7058e9b" rel="nofollow noreferrer">https://medium.com/gitconnected/getting-started-with-web-com...</a>
In general, no. React has been around for over 10 years now, and it generally remains popular and well supported. It is not going anywhere. Some sites will choose to migrate between React and Web-components based frameworks such as Lit for various reasons (technical preferences, standardizing technology stacks within an organization etc). Some sites will combine chunks of UI built with React and chunks of UI built with Web components (eg. by different teams within an organization). Others will create web applications which use Web components for style/DOM isolation at the top level, but where web components are built internally with React (which has various tooling and API advantages over WCs at the lower level).
You can answer this yourself if you think through it from a business perspective.<p>What problem does react solve? It’s an architecture in a box and it helps developers put text into n screen.<p>Why react? Training developers costs time and money when developers are already a cost center. Worse, not all people claiming to do this work are capable of being trained. So, react becomes a means for employers to select ideal candidates.<p>What value does react provide? Candidate selection and a shared architecture.<p>What is lost by not using react? Developers cannot write original applications and struggle to put text on screen.<p>Can web components do that faster or cheaper than react without training overhead? If so then web components will dominate.
Web components have been around longer than React. They have improved over the years, and they both have their pros/cons... but if either one was going to replace the other, that likely would have already occurred.