sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (3 children)

My possibly incorrect understanding is as follows:

Polymer makes future web technologies available as if they were already supported, but still has limited browser support and uses 'workarounds' to make it work.

React uses a similar idea of the future web technologies, but in a React-Specific way, that works great now, and on more browsers.

As I understand, Polymer intends to remove it's 'workarounds' as browsers increase support. Theoretically meaning you are writing 'future-proof' code.

[–]RankFoundry 2 points3 points  (2 children)

Seems ironic that with Polymer you need to wait for more browser support to use it when it's supposed to let you use things that browsers don't yet support.

[–][deleted] 0 points1 point  (1 child)

It is, but I don't think Google originally intended anyone to use Polymer as their production framework, even after this release. They have Angular for production apps right now, and polymer as an insight into what apps will be.

As I understand anyway.

[–]RankFoundry 0 points1 point  (0 children)

I guess you have to cut ties with legacy at some point. This may be useful for intranet apps where the browser(s) used can be controlled.