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

An Introduction to Polymer - A Web Component Library

wearenorthern.com

Post reply on HN
Print view View original

1–10 of 56 posts

Re: An Introduction to Polymer - A Web Component Library

#5

Post by yathern »

I've been using Polymer since 0.5 for a number of personal projects as well as professional.

I have to say it's been a pleasure to use - coming from Angular 1.0. I like it has a very low barrier to entry, having only one real concept; Web Components.

Polymer gives you Data Binding and a few nice things on top of that, but for the most part, you're writing things fairly vanilla.

It's definitely not without it's problems. Element inheritence doesn't really exist in 1.X unless you use Behaviors. There's no inline expression support in bindings. This is partially good because it forces you to keep logic in your javascript, where it belongs. But it also means you sometimes have to be more verbose in obvious places:

   They are not equal
vs

   They are not equal
But even still, I've been able to be very productive with it, and enjoy using it thoroughly. Feel free to ask me about my experience.

Re: An Introduction to Polymer - A Web Component Library

#7

Post by hood_syntax »

yathern wrote: post #5

I've been using Polymer since 0.5 for a number of personal projects as well as professional. I have to say it's been a pleasure to use - coming from Angular 1.0. I like it has a very low barrier to entry, having only one real concept; Web Components. Polymer gives you Data Binding and a few nice things on top of that, but for the most part, you're writing things fairly vanilla. It's definitely not without it's proble…

The idea of Polymer/Web Components appeals to me as a backend developer who has a little experience with JS and Angular 1. Can you tell me a little about how you've used it professionally and what you thought? I.e. scale, scalability, maintainability, encapsulation. I've read a little about Polymer but I haven't spent enough time to grok it. Note: consider me a novice as far as front end goes.

Re: An Introduction to Polymer - A Web Component Library

#8

Post by zacharytamas »

bezzi wrote: post #6

This framework seems very interesting, I wonder why it didn't become popular outside of Google

I think it's mostly due to browser support and developer awareness of Web Components. Chrome has native support (of course) for the four main technologies needed for Web Components, but other browsers are starting to catch on. In the meantime you need a few Polyfills to get full support, which is not ideal.

The support graph is starting to look a lot better, though: https://jonrimmer.github.io/are-we-componentized-yet/

Safari has shipped 2/4 of them already with the Custom Elements v1 spec currently in the Safari Tech Preview and turned on by default. https://webkit.org/blog/7027/introducing-custom-elements/

Re: An Introduction to Polymer - A Web Component Library

#9

Post by ergo14 »

bezzi wrote: post #6

This framework seems very interesting, I wonder why it didn't become popular outside of Google

It is popular outside of google:

https://youtu.be/VBbejeKHrjg?t=9m22s

ING, USA Today, IBM, General Electric, Comcast, Net-A-Porter, BBVA, Coca-Cola, Electronic Arts - one of the biggest players in their industries.

Re: An Introduction to Polymer - A Web Component Library

#10

Post by ergo14 »

zacharytamas wrote: post #8
bezzi wrote: post #6

This framework seems very interesting, I wonder why it didn't become popular outside of Google

I think it's mostly due to browser support and developer awareness of Web Components. Chrome has native support (of course) for the four main technologies needed for Web Components, but other browsers are starting to catch on. In the meantime you need a few Polyfills to get full support, which is not ideal. The support graph is starting to look a lot better, though: https://jonrimmer.github.io/are-we-componentized-ye…

Sure, but look at it this way - with other solutions like lets say React their virtual dom is your "polyfill". Even with polyfills polymer is MUCH smaller than react core ;-) I don't see it as a problem as I've created elements that worked in IE10+ with it.
Post reply on HN