Hi Eric, thanks for those links, reading over those. I've read over a few of those before but even the bottom one didn't really clearly let me understand how developing with both differs. Anyway, I'll do some more reading before commenting on this.
As for performance, sadly by having to use the shadow dom polyfill instead of shady dom (due to using meteor) the CPU usage is pretty high. I have a really expensive workstation laptop but using a site with just a few Polymer custom elements really kills the performance. Even just scrolling a site is really sluggish on Firefox or IE (not sure about Safari). The slowdown is far too much to really launch a site completely built with Polymer as the view layer :( On Monday, 21 September 2015 16:28:49 UTC+8, Eric Bidelman wrote: > > This is a long post with a lot of questions :) Can we start by addressing > performance? What are your concerns? > > Meanwhile, please do some research on the topics. There are a few decent > articles comparing the component models, including a couple of 0.5 articles > that discuss the benefits of web components: > > Understanding Polymer: > https://www.polymer-project.org/0.5/docs/start/everything.html > Understanding Web Components: > https://www.polymer-project.org/0.5/platform/custom-elements.html > > http://addyosmani.com/blog/component-interop-with-react-and-custom-elements/ > https://www.accelebrate.com/blog/web-components-angular-polymer-and-react/ > > http://programmers.stackexchange.com/questions/225400/pros-and-cons-of-facebooks-react-vs-web-components-polymer > > Added Arthur to the thread. Some of the 0.5 material is still pretty good. > There's not a definitive place on the web where users can learn about the > benefits of web components. > > On Mon, Sep 21, 2015 at 6:27 AM <[email protected] <javascript:>> > wrote: > >> Hi guys, I've been using Polymer for a while, pretty much just with the >> elements from the catalog. In terms of production readiness I don't feel >> too happy with Polymer in terms of compatibility and performance but I >> still want to consider it for our next crucial startup project. We >> currently have a site that's built just on bootstrap because we wanted to >> quickly get an MVP out to customers. Now we intend to componentize >> everything and we're looking at two options: React and Polymer. >> >> The thing is, I have no idea how Polymer and React really differ and what >> the pros and cons are. What I'd like to get an emphasis on is the developer >> experience and outlook for the next years from now. Eric Bidelman made a >> public post recently calling React "one of many frameworks" that come and >> go. I understand the point he was trying to make by saying React is simply >> one of the currently hot frameworks and it might vanish, whereas Polymer >> tries to push webcomponents forward so we can all benefit from the same >> components. But what if React will eventually support webcomponents, what >> are the differences? Or more so, are we even going to write Polymer >> components in two years from now? Polymer intend to make webcomponents >> possible in a time where they are not yet ready to be used in every >> browser. On top of that it adds sugar coating to make developing >> webcomponents easier, right? Does that mean Polymer will eventually >> disappear? If I write webcomponents with Polymer, are those components >> eventually usable without Polymer? >> >> What are the pros and cons over using Polymer and React? I don't know >> that much about both in terms of how they keep and transfer states, I just >> know that React keeps everything in one component and keeps all its states >> in each component which seems to make it easy to set and retrieve the state >> of a component. With Polymer it seems to be similar, right? All the states >> are in the components which I retrieve via selecting the element and >> checking for a certain property. Is this how it works in React? What are >> the differences with data binding? There are many things I unfortunately >> don't understand about both of them. Personally I really like Polymer so >> far but I am not sure how production ready it really is. That's why React >> is under consideration, although I've never touched it and I don't know how >> long it is about to stay. However, React components work reliably in most >> browsers (without bad performance?) >> >> If you would try to give me an as objective as possible explanation what >> speaks for and against both Polymer and React, what would it be? >> >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/ddf0cefe-5dfa-4187-bdf7-2ad3d91f8602%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/ddf0cefe-5dfa-4187-bdf7-2ad3d91f8602%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > 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/13e6fb8d-f6ba-44c0-8702-b2ab2d0c16d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
