3 ms·
If you want a mostly pure DOM-based framework, take a look at Polymer, too (http://www.polymer-project.org/ http://www.polymer-project.org/). Web components see
by nevir 13y ago
If you want a mostly pure DOM-based framework, take a look at Polymer, too (http://www.polymer-project.org/ http://www.polymer-project.org/). Web components seem to really embody what the article is driving at.
- platz 13y agoIsn't React a mostly pure DOM-based framework as well?
- catshirt 13y agoit is. one difference i think is that polymer seems to rely on Web Components API and shadow DOM. i guess subviews in React are functionally identical, but React does so without regard for the Web Components API. which has been fine with me. personally, i don't like seeing stuff like this in Polymer: <roster-list persons='[{"name": "John"}, {"name": "Bob"}]'></roster-list> and i like that React let's you write views without data-as-strings.
- saraid216 13y agoAs far as I've been able to tell, React and Polymer basically address the same problem. (And, unfortunately, each community is said to be dismissive of the other. So there's that.) My personal take is that, unless Polymer gets integrated into the browser, React is a better solution because it doesn't try to do custom DOM elements.
- modarts 13y agoNot really: a lot of its value is in the fact that the DOM gets abstracted away as "just another render target" (canvas, and perhaps even eventually native UI's could be potential future targets) React can fully render out to a string of HTML without any dependencies on a DOM implementation (for instance, if you're on the server) (http://facebook.github.io/react/docs/top-level-api.html#react.rendercomponenttostring http://facebook.github.io/react/docs/top-level-api.html#reac...)