Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why Polymer Project (Web Components) isn't famous yet in comparison to other approach?

It's been about a while Polymer version 2 is available out there, but

  • few people talk about it
  • few developers write about it in their blogs
  • few developers share their workflow and their experiences

Polymer Project is powered by Google, and the team seems have impeccable philosophy behind it.

Beside lack of browser support, Polyfills are doing the job still fine.

By the way, It seems people don't prefer to switch on it and work on it although Web components is an standard of the web.

There's a big why for me, there should be an explanation.

This is I think is related to Stackoverflow However I know many wouldn't like this kind of questions.

like image 296
Mehdi Raash Avatar asked Jul 29 '17 10:07

Mehdi Raash


People also ask

What is polymer web components?

Polymer is a lightweight library built on top of the web standards-based Web Components APIs, and makes it easier to build your very own custom HTML elements. Creating reusable custom elements - and using elements built by others - can make building complex web applications easier and more efficient.

What is polymer in web development?

Polymer is an open-source JavaScript library for building web applications using Web Components. The library is being developed by Google developers and contributors on GitHub. Modern design principles are implemented as a separate project using Google's Material Design design principles.

Are polymers outdated?

Polymer is deprecated in favor of LitElement which comes with TypeScript decorators. With LitElement you are still encoding markup in strings and only the interpolated expressions are typechecked [1].

Is Web components the future?

Web components probably are the future of web development; but for the time being it looks like they're going to stay there for most of us.


1 Answers

First, it's actually a very new technology since Polymer 2 was officially released in May of 2017.

Second, the fact that it is supported by Google is not necessarily an advantage: web developers who want to rely on this company's products may prefer Angular, which is also promoted by Google and is much more mature and famous.

Third, the fact that it is founded on the Web components standard is not an advantage too:

  • polyfills are doing the job (though not always) but their use adds a bit of complexity and can introduce a gap in therm of performance between the native and polyfilled implementation of Custom Element and Shadow DOM.

  • developers who know Custom Elements and Shadow DOM may prefer to create Vanilla web components instead as they became very easy to design thanks to... Google :-) That's precisely the purpose of these new web standards.

Fourth, the Material Design flavor chosen for UI elements may not fit everyone's taste.

Fifth, version 2 is not fully compatible with version 1, which may bring some confusion for newcomers, and some disappointments for those who invested on the ephemeral version 1.

Finally, one can question if Polymer is a long-term framework or just a way to support the launch of the early standards (Custom Elements and Shadow DOM) proposed by Google, and promote their adoption.


PS

Some of the above points are only assumptions.

Personally, I started using Polymer 1 during a few months, then I switched to Vanilla Custom Elements.

like image 125
Supersharp Avatar answered Jan 17 '23 22:01

Supersharp