4 ms·

Polymer is built for the world without Vue.js or React. They are slow and heavy weight compared to very very optimized DOM operations done by Vue.js or React.

Polymer is built for the world without Vue.js or React. They are slow and heavy weight compared to very very optimized DOM operations done by Vue.js or React. I think the time for Polymer is gone, and it is better to forget that it exists.

Touche 10y ago
I mean, custom elements just shipped in Chrome a few months ago and are shipping in Safari soon. Firefox is in active development. So a bit too soon to say a technology's time has passed when it hasn't really had a chance up until this point.
- tdumitrescu 10y ago
  Chrome has had Custom Elements since v33, almost 3 years ago. Maybe you're thinking of the latest (v1) iteration of the spec? http://caniuse.com/#feat=custom-elements http://caniuse.com/#feat=custom-elements
  - Touche 10y ago
    Yep, v0 doesn't count, it's a legacy Chrome-only feature for now.
floatboth 10y ago
The performance benefits of virtual DOM / DOM diffing are way, way overrated IMO. You can use that stuff with Polymer where you really need it, but I just use plain Polymer for everything and it's awesome. I think the time for React is gone :-P
- qz_ 10y ago
  Jesus, already? :-P
ergo14 10y ago
Interesting - the benchmarks prove otherwise - it is as fast as other new solutions. So i think you never actually used it in production at any scale. If angular 1.5 was OK for thousands of devs over recent years then Polymer that is comparable to ng2 or react is more then enough. Not to mention that for a world without polymer - some of biggest enterprises in the world are betting on it (and I don't mean just google here).
- netforay 10y ago
  We did use in production. And it sucks to support it. Problems.. * Dynamic components wont work with Vue. Lists etc. * Loading individual html files for each component. Could not figure out how to bundle the components with Webpack. If you still want to use it, use it without Vue or React.
  - ergo14 10y ago
    Well, people use them with angular 1/2 and aurelia so im quite sure it should work with vue/react. I did bundle my components into single file - even throwing in sass compilation so I think the problem is elsewhere ;-)

Touche 10y ago

I mean, custom elements just shipped in Chrome a few months ago and are shipping in Safari soon. Firefox is in active development. So a bit too soon to say a technology's time has passed when it hasn't really had a chance up until this point.

tdumitrescu 10y ago
Chrome has had Custom Elements since v33, almost 3 years ago. Maybe you're thinking of the latest (v1) iteration of the spec? http://caniuse.com/#feat=custom-elements http://caniuse.com/#feat=custom-elements
- Touche 10y ago
  Yep, v0 doesn't count, it's a legacy Chrome-only feature for now.

floatboth 10y ago

The performance benefits of virtual DOM / DOM diffing are way, way overrated IMO. You can use that stuff with Polymer where you really need it, but I just use plain Polymer for everything and it's awesome. I think the time for React is gone :-P

qz_ 10y ago
Jesus, already? :-P

ergo14 10y ago

Interesting - the benchmarks prove otherwise - it is as fast as other new solutions. So i think you never actually used it in production at any scale. If angular 1.5 was OK for thousands of devs over recent years then Polymer that is comparable to ng2 or react is more then enough. Not to mention that for a world without polymer - some of biggest enterprises in the world are betting on it (and I don't mean just google here).

netforay 10y ago
We did use in production. And it sucks to support it. Problems.. * Dynamic components wont work with Vue. Lists etc. * Loading individual html files for each component. Could not figure out how to bundle the components with Webpack. If you still want to use it, use it without Vue or React.
- ergo14 10y ago
  Well, people use them with angular 1/2 and aurelia so im quite sure it should work with vue/react. I did bundle my components into single file - even throwing in sass compilation so I think the problem is elsewhere ;-)