Web Component Solutions: A Comparison

4 years ago dzone.com

Summary: This is a summary of an article originally published by the source. Read the full original article here →

Any time you have code you find yourself duplicating in several places, it’s time to abstract that code away into a class or a function. But how does this apply to user interfaces?

Or what if you want to write a component that is framework-agnostic and can be used in any web app regardless of what it’s written in?

In addition to lacking full browser support, one con of native web components is that they are written using an imperative style.

These libraries offer a better developer experience when creating new web components and often include polyfills that allow the web components to work in browsers that wouldn’t support them out of the box.

DevOps Articles