Photo by James Pond on Unsplash

The State of Web Components

Has the time come to embrace native components?

Michael Karén
The Startup
Published in
7 min readJul 22, 2019

--

Has the modern Web Platform evolved to the point where we can start using native components? As developers, we know that reusing code is a good idea. Does this mean we should use Web Components everywhere, or is this taking it a step too far?

These are some of the questions I try to answer in this article. However, for those who are wondering what I am talking about, let’s start from the beginning.

Why Web Standards?

Before there were any rules, the browser manufacturers kept introducing new features to better their competition. Browsers were diversified, and developers often had to make multiple versions of websites.

Web standards were finally introduced to protect the web ecosystem. Browser makers started working in a more standardized way unifying the browser stack.

The key groups for web standards are:

  • The World Wide Web Consortium (W3C)
  • The Web Hypertext Application Technology Working Group (WHATWG).

These are the community of people producing the standards that build up the web platform.

Web Components

--

--

Michael Karén
The Startup

Frontend Architect • JavaScript Enthusiast • Educative.io Author • ngVikings organizer.