I had the same question, and got the same dismissive answers. I don't think people engaged in either community are optimistic about the other since one invades part of the others space.
You wrote: - Native browser support (read "guaranteed to be faster") That's backwards, if you're talking about dom manipulation. The whole reason for a synthesized dom is because native dom is such a bloated pig. That's React's big selling point. That, and less intrusive than Angular. Again, when I asked your question, all I got were dismissive answers, so apparently no one in that camp was sure. (..."But Brawndo has electrolytes!" :) Post more if you find something interesting! On Friday, January 24, 2014 3:53:45 PM UTC-5, cletusw wrote: > > Just posted a question on StackOverflow that could use an answer by > someone familiar with both Polymer and Facebook's React library: > > What are the main benefits of Facebook's React over the upcoming Web > Components spec and vice versa (or perhaps a more apples-to-apples > comparison would be to Google's Polymer library)? > > > http://stackoverflow.com/questions/21342288/pros-and-cons-of-facebooks-react-vs-web-components-polymer > > Clayton > > 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/b69a0c23-5df3-4994-8ef2-f5f642b1e7f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
