Live data from Hacker News

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

news.ycombinator.com

61–70 of 82 posts

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

#61
post #34

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.

Slow UI or slow loading? Slow loading is due to all the HTML imports generating HTTP requests. This can be optimised by inlining the web-components, using a tool like https://github.com/Polymer/vulcanize I'm not sure why the polymer website is not optimised like this. [edit] Here's what vulcanize does: http://polymer-twitter.badsyntax.co:8002/build.html (Code here: https://github.com/badsyntax/polymer-twitter ) Conca…

I also made a gem for rails called Emcee that does inlining and concatenation: http://github.com/ahuth/emcee.

It also let's you use CoffeeScript or SASS (or anything else that Sprockets recognizes).

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

#62
post #56

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.

React seems so complicated in comparison to Angular templates. Am I wrong?

Try ractive. You get simple mustache templates, but the speed of a virtual DOM like React.

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

#63
post #46
post #19

Earlier quoted context omitted.

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…

Why the hostile reaction? Expanding your horizons is not a bad thing. > Most javascript developers want to use Javascript OP mentions nothing, parent mentions CoffeeScript. Dart also has packages and an official package manager. It also has a dogfooded official Polymer library. Setting up a modular toy project with packages was easier to understand in Dart than JS for me. I don't see how I'm "bloody well not helping"…

[deleted]

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

#64
post #46
post #19

Earlier quoted context omitted.

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…

Why the hostile reaction? Expanding your horizons is not a bad thing. > Most javascript developers want to use Javascript OP mentions nothing, parent mentions CoffeeScript. Dart also has packages and an official package manager. It also has a dogfooded official Polymer library. Setting up a modular toy project with packages was easier to understand in Dart than JS for me. I don't see how I'm "bloody well not helping"…

"polymer has these integration pain points" "you should try dart! it integrates well"

you definitely told shadowmint to go fuck himself.

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

#65
post #19

Earlier quoted context omitted.

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.

If you are a webdeveloepr that builds non-Javascript tools that don't integrate with the rest of Javascript tooling, you will have a very isolated, limited, unadopted and narrow-minded niche you carve for yourself.

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

#66
post #53
post #51

Earlier quoted context omitted.

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 po…

Polymer includes a Web Components polyfill, so you can write raw Web Components if you want to. Polymer is really just some syntactic sugar over that (and other specs thrown in, like html imports, templates, etc).

That said, these aren't really the same kind of libraries at all, so I'm not sure why this is such a x vs y thread. Ideally, react and web components are fully composable, and it doesn't really matter where the element came from.

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

#67
post #51
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…

It doesn't matter if they keep pushing a standard no one's using to actually ship. The only people I see excited about Web Components are Googlers.

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

#68
post #51

Earlier quoted context omitted.

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…

It doesn't matter if they keep pushing a standard no one's using to actually ship. The only people I see excited about Web Components are Googlers.

Then you may not be aware of Mozilla's continued interest in WebComponents[0][1].

[0]: http://mozbrick.github.io/ [1]: http://www.x-tags.org/

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

#69
post #42

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?)

People keep confusing this it seems. What Google is doing here is NOT like what Microsoft did. Google is merely implement many new HTML5 features ahead of Microsoft (which is usually the most behind in HTML5 support) and others.

So it's not that they are "built for Chrome". It's that they are built for "new HTML5 specs" and only Chrome happens to support them right now. Point me to where Silverlight was an HTML spec?

Now, things like NaCl on the other hand are a lot more similar to what Microsoft used to do, but there's still a major difference, and that is that what they are building is open source and everyone can do their own implementation of it. You could never do that with ActiveX or Silverlight. Plus, you could also say Firefox is doing the same as Google with asm.js, which nobody else has adopted so far.

These things are a little more like that, but at least they are open source. The HTML5 features, though, just happen to be implemented faster by Chrome.

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

#70
post #61
post #34

Earlier quoted context omitted.

Slow UI or slow loading? Slow loading is due to all the HTML imports generating HTTP requests. This can be optimised by inlining the web-components, using a tool like https://github.com/Polymer/vulcanize I'm not sure why the polymer website is not optimised like this. [edit] Here's what vulcanize does: http://polymer-twitter.badsyntax.co:8002/build.html (Code here: https://github.com/badsyntax/polymer-twitter ) Conca…

I also made a gem for rails called Emcee that does inlining and concatenation: http://github.com/ahuth/emcee . It also let's you use CoffeeScript or SASS (or anything else that Sprockets recognizes).

It's snazzy :)
Post reply on HN