Microsoft's Edge browser team is on a mission to swap out React UI components with native web platform components. We speak to the team lead.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

Microsoft's Edge browser team aims to replace React components with native web components through the WebUI 2.0 project for better performance and reduced JavaScript reliance. The initiative is driven by the desire to improve the browser's speed, particularly on low-end machines where React caused significant slowdowns. Despite challenges, including the complexity of making web components perform well, the team has seen benefits in developer productivity by focusing on HTML and CSS. Microsoft's broader goal includes making some WebUI 2.0 components open source and encouraging other teams, both internal and external, to adopt web components.

How Microsoft Edge Is Replacing React With Web Components

Why Did Microsoft Edge Decide to Ditch React?

<p>The Edge developer team is shifting towards using Web Components instead of React in the development of some of their own web applications and sites, a good choice for certain use cases.
Not that, MS Edge is replacing React</p>
