Actually… there was an interesting quite extensive framework comparison a month ago or so, React has a larger footprint than Polymer and performance is equal, in fact Polymer even performed slightly better in most cases.
Polymer with shady DOM and React are essentially doing very similar things how they render components to the screen. Both have to generate complex DOM constructs. The difference is simply in how they’re processing/generating the DOM structure.
I want to use Polymer for the same reason I picked Meteor. It was bleeding edge and promised to build apps with state-of-the-art technology. I’m not complaining, I’m being disappointed and showing my frustration.
Polymer promises a more future-proven and safer way to write apps. In four years from now we’ll have another discussion and frustration in the community when everyone no longer uses React and people moved on to the next framework or a webcomponent focused approach - I’m not saying React is bad, it’s obviously great piece of technology. But it could even be replaced by new FB technology in the future.
Now I’m not saying this won’t be similar with Polymer, Polymer itself is somewhat an opinionated library or framework and we will definitely see code-rewrites along the way especially once more features get baked in right into the official webcomponents spec but at least it won’t be as much of a disaster as going from React to any other framework and these code migrations are already a carefully considered plan based on the philosophy behind webcomponents.
I want bleeding edge tech. React is bleeding edge no doubt but essentially both React and Polymer do a lot of the same things (actually Polymer can do a lot more than React can do. Again, not saying it’s better, you could argue for pure view layer React is better but it actually has a lot more extensibility in terms of what you can achieve with it). So I’m just a bit disappointed to see Polymer completely ignored and React completely embraced. In my opinion the first-class support in order according to priortity should be:
It’s ok that first-class support is somewhat based on popularity and that’s a valid reason for Meteor to do but it’s also somewhat short-sighted in my opinion.
Btw in regards to your Polymer/Famous comparison. I would say your comparison is not quite fair. Polymer was never hyped, webcomponents were but it didn’t make progress not because of the library itself but because of the disagreement of webcomponents. Which arguably is a good thing, since theyre a fundamental new technology that’ll shape web development for a while.
Polymer does get continously improved and the community while not as big as React of course is very active, whereas famo.us is simply one serious failure of a product launched and never improved or at least communicated well with the community.
P.S.: I’ve just visited their new website famous.co and had a serious WTF moment LOL