Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Should I use Polymer for my next project?

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 82 posts

Re: Ask HN: Should I use Polymer for my next project?

#51

Post by ffreire »

Flow wrote: post #48
shadowmint wrote: post #3

A couple of down sides of web components: - they interact poorly with requirejs and amd in general. - they flat out dont work at all in IE8 - there's no 'good' solution for the request hell you get from loading 50 components; although some of the tooling is getting there (vulcanize). - the tooling in general is currently rubbish; no way to easily combine sass + jade + coffee into a web component (eg. with gulp, no th…

With ReactJS you get to code as if everything is a component, why use polymer now instead of that?

ReactJS is a solid solution if you need to ship something _today_, but I think the trend will continue towards WebComponents as they become standardized across vendors (if not Polymer then x-tags, if not x-tags then... etc). In that sense, it's better to familiarize oneself with the technologies that we'll be seeing more of in the future just as we did with new HTML5 elements a few years ago.

@jastanton phrased it nicely in another comment here: https://news.ycombinator.com/item?id=7971847

Re: Ask HN: Should I use Polymer for my next project?

#52

Post by spankalee »

tkinom wrote: post #42
chrismonsanto wrote: post #9

The Polymer website uses Polymer and it is slooooow. That's a huge red flag to me. I have nothing but good things to say about React. Try that instead.

Agree, Designer tool looks kinda nice. BUT, it is slow in FF30, Safari and failed a lot in IE11. IMO, Big G is trying very hard to push web technologies that tightly couple to Chrome - same as what MS/IE did a few years back trying hard to force ActiveX, Silverlight down the developers' throat. I'm betting < 20% chance Polymer will still be in IO talk 3 years from now. (remember GWT, Dart, Angular?)

Hi, I'm on the Dart team and spoke at IO this year. Remember what? :)

You have to remember that Polymer is a library that helps you implement Web Components. The APIs for Web Components are being integrated directly into the browser. Chrome already has them, and Firefox is landing them now. Even Microsoft is interested.

This is not another framework.

edit: Check out http://jonrimmer.github.io/are-we-componentized-yet/ for a summary of the progress on the Web Components standards.

Re: Ask HN: Should I use Polymer for my next project?

#53

Post by Flow »

ffreire wrote: post #51
Flow wrote: post #48

Earlier quoted context omitted.

With ReactJS you get to code as if everything is a component, why use polymer now instead of that?

ReactJS is a solid solution if you need to ship something _today_, but I think the trend will continue towards WebComponents as they become standardized across vendors (if not Polymer then x-tags, if not x-tags then... etc). In that sense, it's better to familiarize oneself with the technologies that we'll be seeing more of in the future just as we did with new HTML5 elements a few years ago. @jastanton phrased it ni…

As I see it, the inside of Web Components still need a nice and structured way to function. I'd build my app using ReactJS now, and when I decide to use web components, I can transform each separate ReactJS component into a web component, ReactJS-tag for ReactJS-tag as I see fit.

It's much safer to do it this way than rely on polymer. IMHO. When web components really are here for everyone, you are still stuck with polymer libs and tools and all the code is bound to them. Who knows, polymer might be considered bloat then?

Re: Ask HN: Should I use Polymer for my next project?

#54

Post by STRML »

dfreedm2 wrote: post #28
STRML wrote: post #4

I used it for a project about a year ago ( https://github.com/STRML/securesha.re-client/tree/master/pol... ). I found that it was difficult to keep the service up and working; while older browsers still seem to load it quite well, Chrome continues to natively implement parts of the (changing) spec. When Polymer detects native capability for a given feature, it turns its polyfills off. But if the spec has changed, you…

Sorry to hear about that. Thankfully the specs are done now that everything is shipping in Chrome 36. I hope you'll find some useful web components in the future that you can just drop in to whatever project you're working on and save some time!

Is that so - are the specs final now?

Re: Ask HN: Should I use Polymer for my next project?

#55

Post by vittore »

chrismonsanto wrote: post #9

The Polymer website uses Polymer and it is slooooow. That's a huge red flag to me. I have nothing but good things to say about React. Try that instead.

Talking about React, there is nice react binding for Kendu.UI library that guys from WingSpan are working on https://github.com/wingspan/wingspan-forms You can see demo here: http://wingspan.github.io/wingspan-forms/examples/form-maste... (more demo links on github page)

Re: Ask HN: Should I use Polymer for my next project?

#57

Post by [deleted] »

joemaller1 wrote: post #7

I really liked the Polymer demos from I/O, but stepping back, it seems an awful lot like React without the compatibility. Polymer does appear to be more than just another Google flash-in-the-pan. They've got a good team, which is working closely with the Chrome team and Google's investment at I/O was significant. I wonder how the Angular folks are feeling. Facebook is using React right now, when will Google put Polym…

[deleted]

Re: Ask HN: Should I use Polymer for my next project?

#58

Post by dustingetz »

chrismonsanto wrote: post #9

The Polymer website uses Polymer and it is slooooow. That's a huge red flag to me. I have nothing but good things to say about React. Try that instead.

Polymer and React are orthogonal, here is a great comment explaining the difference: https://news.ycombinator.com/item?id=7739755

Re: Ask HN: Should I use Polymer for my next project?

#59

Post by Cthulhu_ »

rektide wrote: post #19
DCKing wrote: post #5

Earlier quoted context omitted.

> - they interact poorly with requirejs and amd in general. > - the tooling in general is currently rubbish; no way to easily combine sass + jade + coffee into a web component (eg. with gulp, no the dart bindings don't count as tooling). no way to have external resource files. If you use Dart and its Polymer libraries, these two things should not be a problem. Why does that not count? He didn't say he wants to use Sa…

Most javascript developers want to use Javascript and want to use what's available in the defacto javascript package manager (npm) and want to use the build tool that works with the javascript packages (browserify). Suggesting using something other than Javascript, it's packages, and it's preeminent packager to get started with Polymer is exactly the problem parent was highlighting, and your suggestion is bloody not…

IMHO, if you (nonpersonal you) identify as a Javascript developer instead of a web developer, you're a very limited and narrow-minded developer. Learning a new language is easy, and installing some new tooling shouldn't take more than a minute nowadays. Looks like Polymer is installed using Bower anyway, which is pretty standard.
Post reply on HN