About the direction of the polymer

2 min read Original article ↗

Dear Community,

Polymer direction: https://www.youtube.com/watch?v=JH6jEcLxJEI

So sad. The main reason I select polymer to develop the webapp is that It keeps the html part without js. The front end developer can keep their logic in the js side and the designer can continue html design section but now the rendering part mix with js again. Might be I should move back to react as the only uniqueness of polymer is gone.

Personally, I don't think polymer 3.0 following react style can earning users as react already have the majority of the front-end market and it is true. Polymer should keep the HTML native concepts in order to survive in the front-end world.

Finally, I always think Polymer is based on two concepts

  1. <iframe>
  2. Shadows Dom

As customize Dom is following the iframe that developer can packaging the HTML code and import it anywhere.

Reference : https://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-301/

Polymer 2016 : https://youtu.be/Ihdp63FaRKA?t=25m39s

However, I don't think Polymer will listen my opinion as I remember it has a debate about golang direction.
The final response from Google is that "If you do not agree, you can fork your own". Therefore, I just want to leave a record for my view about Polymer 3.0.

Thanks
Alpha