Polymer vs Web Components

Overview

Polymer

Stacks557

Followers463

Votes122

GitHub Stars22.1K

Forks2.0K

Web Components

Stacks82

Followers60

Votes0

Polymer vs Web Components: What are the differences?

Developers describe Polymer as "A new library built on top of Web Components, designed to leverage the evolving web platform on modern browsers". Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds. On the other hand, Web Components is detailed as "A set of web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web apps". Web components are a set of web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps.

Polymer and Web Components belong to "Front-End Frameworks" category of the tech stack.

Polymer is an open source tool with 21.4K GitHub stars and 2.02K GitHub forks. Here's a link to Polymer's open source repository on GitHub.

Bloomberg LP, MobilePay, and Lumeneo.com are some of the popular companies that use Polymer, whereas Web Components is used by Mogic GmbH, Health Dynamics, and Invia Flights Germany GmbH. Polymer has a broader approval, being mentioned in 61 company stacks & 296 developers stacks; compared to Web Components, which is listed in 15 company stacks and 11 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Polymer, Web Components

Gericke

Jul 27, 2020

Needs adviceon

.NET Core

JavaScript

React

Hi,

I am looking into solutions for reusable components for an existing #MVC project which is build on .NET Core. Currently some functionality is being reuses via JavaScript. I have React experience so I know I can create React components and then reference it on the MVC app. The only problem is I do not know the full extent of it as the current app uses a lot of 3rd party libraries, not sure how that will effect React components. I am currently looking into WebComponents which is also another way for creating reusable components and it is compatible with any JavaScript library based on what I have seen on the website. Also to take in consideration that it should cause a re-write of the system.

So my question is, to future-proof reusable components, which will be best React or Web Components? And which will be more reliable to use with 3rd party libraries?

49.1k views49.1k

Comments

Detailed Comparison

Polymer	Web Components
Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds.	Web components are a set of web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps.
Statistics
GitHub Stars 22.1K	GitHub Stars -
GitHub Forks 2.0K	GitHub Forks -
Stacks 557	Stacks 82
Followers 463	Followers 60
Votes 122	Votes 0
Pros & Cons
Pros 52 Web components 30 Material design 14 HTML 13 Components 5 Open source Cons 1 Last version is like 2 years ago? that's totally rad	No community feedback yet

What are some alternatives to Polymer, Web Components?

Bootstrap

Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.

Foundation

Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices.

Semantic UI

Semantic empowers designers and developers by creating a shared vocabulary for UI.

Materialize

A CSS Framework based on material design.

Material Design for Angular

Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs.

Material-UI

Material UI is a library of React UI components that implements Google's Material Design.

Blazor

Blazor is a .NET web framework that runs in any browser. You author Blazor apps using C#/Razor and HTML.

Quasar Framework

Build responsive Single Page Apps, SSR Apps, PWAs, Hybrid Mobile Apps and Electron Apps, all using the same codebase!, powered with Vue.

Nuxt.js

Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more.

UIkIt

UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable.

Related Comparisons

Polymer is an open source tool with 21.4K GitHub stars and 2.02K GitHub forks. Here's a link to Polymer's open source repository on GitHub.

Polymer vs Web Components