Phoenix Framework vs Polymer

Overview

Polymer

Stacks557

Followers463

Votes122

GitHub Stars22.1K

Forks2.0K

Phoenix Framework

Stacks1.0K

Followers1.0K

Votes678

GitHub Stars22.6K

Forks3.0K

Phoenix Framework vs Polymer: What are the differences?

MVC Architecture: Phoenix Framework follows a Model-View-Controller architecture, which helps in separating concerns by defining separate layers for data manipulation, user interface, and business logic. On the other hand, Polymer follows a component-based architecture, where reusable web components are created and used throughout the application.
Server-side vs Client-side: Phoenix Framework is a server-side framework built on Elixir and provides robust server-side capabilities such as routing, database interactions, and session management. In contrast, Polymer is a client-side library that helps in building dynamic, interactive user interfaces directly in the browser with Web Components and templates.
Data Binding: Polymer provides two-way data binding out of the box, which means changes in the model are reflected in the view and vice versa. Phoenix Framework does not offer built-in two-way data binding like Polymer; developers need to handle data binding manually.
Language: Phoenix Framework is written in Elixir, a functional programming language built on top of Erlang VM, which provides fault-tolerant and distributed capabilities. Polymer, on the other hand, is primarily based on JavaScript and leverages modern web technologies like Web Components and Shadow DOM.
Community and Ecosystem: Phoenix Framework has a smaller community compared to Polymer, which is supported by Google. Polymer has a vast ecosystem of tools, libraries, and resources, making it easier for developers to find solutions and support for their projects. Phoenix, while growing, may have limited resources and support compared to Polymer.

In Summary, Phoenix Framework and Polymer differ in their architecture, server-side vs client-side nature, data binding capabilities, programming language, and community support.

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, Phoenix Framework

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.2k views49.2k

Comments

Detailed Comparison

Polymer	Phoenix Framework
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.	Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.
Statistics
GitHub Stars 22.1K	GitHub Stars 22.6K
GitHub Forks 2.0K	GitHub Forks 3.0K
Stacks 557	Stacks 1.0K
Followers 463	Followers 1.0K
Votes 122	Votes 678
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 120 High performance 76 Super fast 70 Rapid development 62 Open source 60 Erlang VM Cons 6 No jobs 5 Very difficult
Integrations
No integrations available	Elixir

What are some alternatives to Polymer, Phoenix Framework?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Bootstrap

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

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Related Comparisons

Phoenix Framework vs Polymer: What are the differences?

MVC Architecture: Phoenix Framework follows a Model-View-Controller architecture, which helps in separating concerns by defining separate layers for data manipulation, user interface, and business logic. On the other hand, Polymer follows a component-based architecture, where reusable web components are created and used throughout the application.
Server-side vs Client-side: Phoenix Framework is a server-side framework built on Elixir and provides robust server-side capabilities such as routing, database interactions, and session management. In contrast, Polymer is a client-side library that helps in building dynamic, interactive user interfaces directly in the browser with Web Components and templates.
Data Binding: Polymer provides two-way data binding out of the box, which means changes in the model are reflected in the view and vice versa. Phoenix Framework does not offer built-in two-way data binding like Polymer; developers need to handle data binding manually.
Language: Phoenix Framework is written in Elixir, a functional programming language built on top of Erlang VM, which provides fault-tolerant and distributed capabilities. Polymer, on the other hand, is primarily based on JavaScript and leverages modern web technologies like Web Components and Shadow DOM.
Community and Ecosystem: Phoenix Framework has a smaller community compared to Polymer, which is supported by Google. Polymer has a vast ecosystem of tools, libraries, and resources, making it easier for developers to find solutions and support for their projects. Phoenix, while growing, may have limited resources and support compared to Polymer.

In Summary, Phoenix Framework and Polymer differ in their architecture, server-side vs client-side nature, data binding capabilities, programming language, and community support.

Phoenix Framework vs Polymer

Overview