Lit vs Polymer

Overview

Polymer

Stacks557

Followers463

Votes122

GitHub Stars22.1K

Forks2.0K

Lit

Stacks126

Followers36

Votes4

GitHub Stars2.0K

Forks94

Lit vs Polymer: What are the differences?

Data Binding: Lit uses a simple syntax for data binding where the templating system automatically updates the UI when the data changes, while Polymer requires additional code for two-way data binding.
Performance: Lit offers superior performance due to its lightweight nature and efficient rendering system, whereas Polymer can be heavier and slower due to its full-featured nature, which includes unnecessary features for some applications.
Size: Lit has a smaller file size as it includes only the essentials for web components, resulting in quicker load times, whereas Polymer includes a larger set of features which might not be required, making it a bit heavier in comparison.
Directives: Lit utilizes standard web platform features like Lit directives, making it more aligned with modern best practices, whereas Polymer has its own set of custom elements and directives, which might require additional learning and maintenance.
Composition Patterns: Lit encourages the use of composition patterns for building complex components, leading to better code structure and reusability, while Polymer can sometimes lead to monolithic components that are harder to maintain and reuse.
Community Support and Updates: Lit is actively maintained by a team at Google, providing regular updates and support, whereas Polymer has seen a decrease in active development and focus from Google, leading to uncertainties in its long-term support and compatibility.

In Summary, Lit and Polymer differ in their approach to data binding, performance, file size, directives, composition patterns, and community support, with Lit being more streamlined and aligned with modern practices compared to Polymer.

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, Lit

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	Lit
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.	A tiny CSS framework that preserves everything Skeleton, Milligram, and other micro frameworks have to offer.
Statistics
GitHub Stars 22.1K	GitHub Stars 2.0K
GitHub Forks 2.0K	GitHub Forks 94
Stacks 557	Stacks 126
Followers 463	Followers 36
Votes 122	Votes 4
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	Pros 2 Lit-html 2 Performance

What are some alternatives to Polymer, Lit?

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

Lit vs Polymer: What are the differences?

Data Binding: Lit uses a simple syntax for data binding where the templating system automatically updates the UI when the data changes, while Polymer requires additional code for two-way data binding.
Performance: Lit offers superior performance due to its lightweight nature and efficient rendering system, whereas Polymer can be heavier and slower due to its full-featured nature, which includes unnecessary features for some applications.
Size: Lit has a smaller file size as it includes only the essentials for web components, resulting in quicker load times, whereas Polymer includes a larger set of features which might not be required, making it a bit heavier in comparison.
Directives: Lit utilizes standard web platform features like Lit directives, making it more aligned with modern best practices, whereas Polymer has its own set of custom elements and directives, which might require additional learning and maintenance.
Composition Patterns: Lit encourages the use of composition patterns for building complex components, leading to better code structure and reusability, while Polymer can sometimes lead to monolithic components that are harder to maintain and reuse.
Community Support and Updates: Lit is actively maintained by a team at Google, providing regular updates and support, whereas Polymer has seen a decrease in active development and focus from Google, leading to uncertainties in its long-term support and compatibility.

Lit vs Polymer

Overview