5 ms·

If you like component approach, take a look at Polymer, I'm right now working with react, and while it is OK, I've found that web standards based approache to c

by ergo14 10y ago

If you like component approach, take a look at Polymer, I'm right now working with react, and while it is OK, I've found that web standards based approache to components is better. And web components can be used in react or other solutions nicely. Being "anti-react" doesn't mean anti-component approach. You can do same with angular 1.5+, vue, aurelia or others.

jondubois 10y ago
That's a good point. I don't think many people actually dislike React. There are people like me who might be mildly frustrated that React is getting so much attention when Vue.js and Polymer might be better, simpler solutions. I like React (especially with all the new setup and debugging tooling) but whenever I use it, I feel that it is a small step down from Polymer. I think that unfortunately Polymer 0.5 was launched too early and its reputation has been tainted even though Polymer 2.0 is amazing. I do know that there are also developers in the Vue.js camp who would never use React out of principle. I spoke with HR people from Facebook in the past and they've told me that there are developers who simply refuse to use React but I think it's more a matter of stubbornness because, all things considered, it is roughly comparable to Polymer and Vue.js.
nojvek 10y ago
Is polymer really a Web standard? Seems like something Google is pushing down. The implementation is quite fragmented. I'd love browser makers to focus on the basics like rendering, js and asm.js and leave the rest to libs.
- ergo14 10y ago
  No - Polymer is not a web standard - Web components are (https://www.webcomponents.org/specs https://www.webcomponents.org/specs) - and are implemented as a standard (its not fragmented all vendors agreed on v1.0, chrome, safari, opera already ship with them, MS and FX are close to follow) - polymer is just 30kb on top of that to make your life easier. This is exactly what you described with asm.js. It just happens that out of all libraries that help you create web components, polymer is probably most widely used - well, angular 2.x can technically output web components too, but I don't want to compare a framework with library. But you can mix those components with other solutions (like x-tags, skatejs, bosonic, "pure components" etc.), they are interoperable, I even have them cooperate with legacy jquery application.
justsee 10y ago
In the context of Next.js's serverside-rendering approach, Polymer has an open ticket about providing support for SSR: https://github.com/Polymer/polymer/issues/3955 https://github.com/Polymer/polymer/issues/3955.

by ergo14 10y ago

jondubois 10y ago

That's a good point. I don't think many people actually dislike React. There are people like me who might be mildly frustrated that React is getting so much attention when Vue.js and Polymer might be better, simpler solutions. I like React (especially with all the new setup and debugging tooling) but whenever I use it, I feel that it is a small step down from Polymer. I think that unfortunately Polymer 0.5 was launched too early and its reputation has been tainted even though Polymer 2.0 is amazing. I do know that there are also developers in the Vue.js camp who would never use React out of principle. I spoke with HR people from Facebook in the past and they've told me that there are developers who simply refuse to use React but I think it's more a matter of stubbornness because, all things considered, it is roughly comparable to Polymer and Vue.js.

nojvek 10y ago

Is polymer really a Web standard? Seems like something Google is pushing down. The implementation is quite fragmented. I'd love browser makers to focus on the basics like rendering, js and asm.js and leave the rest to libs.

ergo14 10y ago
No - Polymer is not a web standard - Web components are (https://www.webcomponents.org/specs https://www.webcomponents.org/specs) - and are implemented as a standard (its not fragmented all vendors agreed on v1.0, chrome, safari, opera already ship with them, MS and FX are close to follow) - polymer is just 30kb on top of that to make your life easier. This is exactly what you described with asm.js. It just happens that out of all libraries that help you create web components, polymer is probably most widely used - well, angular 2.x can technically output web components too, but I don't want to compare a framework with library. But you can mix those components with other solutions (like x-tags, skatejs, bosonic, "pure components" etc.), they are interoperable, I even have them cooperate with legacy jquery application.

justsee 10y ago

In the context of Next.js's serverside-rendering approach, Polymer has an open ticket about providing support for SSR: https://github.com/Polymer/polymer/issues/3955 https://github.com/Polymer/polymer/issues/3955.