Polymer vs Semantic UI: What are the differences?
Polymer: 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; Semantic UI: A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI.
Polymer and Semantic UI can be primarily classified as "Front-End Frameworks" tools.
"Web components" is the top reason why over 48 developers like Polymer, while over 134 developers mention "Easy to use and looks elegant" as the leading cause for choosing Semantic UI.
Polymer and Semantic UI are both open source tools. Semantic UI with 45.7K GitHub stars and 4.83K forks on GitHub appears to be more popular than Polymer with 21.1K GitHub stars and 2K GitHub forks.
According to the StackShare community, Semantic UI has a broader approval, being mentioned in 77 company stacks & 50 developers stacks; compared to Polymer, which is listed in 41 company stacks and 30 developer stacks.
What is Polymer?
What is Semantic UI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Polymer?
What are the cons of using Semantic UI?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Polymer?
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
In process of Learning Technics- Studing to know more. I was introduced in a Google event.
Polymer is another Google offering that focuses on Web Components, an up-and-coming collection of technologies that provide web developers with the ability to create customer HTML elements.
Polymer is super future-focused and really great to build in. The biggest plus for us is how its component-focused approach keeps things modular and maintainable. It also makes it really easy to implement material design.
We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.