Flakes vs Polymer

Overview

Polymer

Stacks557

Followers463

Votes122

GitHub Stars22.1K

Forks2.0K

Flakes

Stacks8

Followers11

Votes3

GitHub Stars1.8K

Forks82

Flakes vs Polymer: What are the differences?

# Introduction

Key differences between Flakes and Polymer:

1. **Architecture**: Flakes follows a modular architecture, where functionalities are divided into independent modules, while Polymer follows a component-based architecture, where components are the building blocks of the application.
   
2. **Data Binding**: Flakes uses a one-way data binding approach, meaning changes in the model are automatically reflected in the view, whereas Polymer supports both one-way and two-way data binding for efficient data handling.
   
3. **Styling**: Flakes utilizes CSS preprocessors like Sass or Less for styling components, offering more flexibility in design customization. On the other hand, Polymer encourages the use of Material Design principles and provides a set of predefined styling options for components.
   
4. **Browser Support**: Flakes is well-supported in modern browsers, but it may require additional polyfills for older versions, while Polymer is designed to work seamlessly across all major browsers without the need for extensive polyfills.
   
5. **Community and Ecosystem**: Flakes has a smaller community and ecosystem compared to Polymer, which has a larger community support, extensive documentation, and a wider range of ready-to-use components and tools.
   
6. **Performance**: Polymer is optimized for performance, with features like lazy-loading components and efficient data binding mechanisms, providing a smoother user experience compared to Flakes.

In Summary, Flakes and Polymer differ in their architecture, data binding approach, styling options, browser support, community size, and performance optimizations.

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

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	Flakes
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.	Flakes is an Admin Template Framework. A combination of CSS Libraries, JavaScript Libraries and Design files that help you build business tools very quickly.
Statistics
GitHub Stars 22.1K	GitHub Stars 1.8K
GitHub Forks 2.0K	GitHub Forks 82
Stacks 557	Stacks 8
Followers 463	Followers 11
Votes 122	Votes 3
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 1 High information density 1 Minimalist to almost the extreme 1 Good integration with gridforms Cons 1 Not comprehensive 1 Seemingly small to no community

What are some alternatives to Polymer, Flakes?

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

Flakes vs Polymer: What are the differences?

# Introduction

Key differences between Flakes and Polymer:

1. **Architecture**: Flakes follows a modular architecture, where functionalities are divided into independent modules, while Polymer follows a component-based architecture, where components are the building blocks of the application.
   
2. **Data Binding**: Flakes uses a one-way data binding approach, meaning changes in the model are automatically reflected in the view, whereas Polymer supports both one-way and two-way data binding for efficient data handling.
   
3. **Styling**: Flakes utilizes CSS preprocessors like Sass or Less for styling components, offering more flexibility in design customization. On the other hand, Polymer encourages the use of Material Design principles and provides a set of predefined styling options for components.
   
4. **Browser Support**: Flakes is well-supported in modern browsers, but it may require additional polyfills for older versions, while Polymer is designed to work seamlessly across all major browsers without the need for extensive polyfills.
   
5. **Community and Ecosystem**: Flakes has a smaller community and ecosystem compared to Polymer, which has a larger community support, extensive documentation, and a wider range of ready-to-use components and tools.
   
6. **Performance**: Polymer is optimized for performance, with features like lazy-loading components and efficient data binding mechanisms, providing a smoother user experience compared to Flakes.

In Summary, Flakes and Polymer differ in their architecture, data binding approach, styling options, browser support, community size, and performance optimizations.

Flakes vs Polymer

Overview