My take (disclosure: met Polymer team, and helped them out). I've looked at React, but never used it in an interesting project.
Major difference is treatment of DOM: Polymer embraces DOM, React treats DOM as a compile target. From this, it follows: - Polymer is easier to work with if you know DOM (developer productivity is higher) - React can compile to native apps, Polymer can't. - Web Components will last as long as browsers. React will not. React is more mature (stability, bugs), and has been used publicly for a couple of years, Polymer 1.0 has been out for 4 months, there are still bugs in the core/iron. I run into a couple of interesting ones every week. I've been helping people wrestling with this for a couple of months. My take: - if you are shipping soon, pick the framework that's easiest to implement your app in. What are your devs happy with? Which one has the components you want? Is there a sample app that looks like what you are doing? Both frameworks will be fast enough. - if you are writing a classic web app, something that you'll have to maintain for a long time, use Polymer. When both React and Polymer are gone, your migration path to the shiny new web components framework will be a lot easier with Polymer. Aleks Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/343d5bbf-0231-4c8d-a452-33b51089170c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
