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

21–30 of 56 posts

Re: An Introduction to Polymer - A Web Component Library

#21

Post by cdata »

Pigo wrote: post #19
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…

I first looked at Polymer quite awhile ago, maybe over a year. I guess I kind of thought it was a stepping stone to Angular 2 which uses a component model, like most of the other latest frameworks. Or that maybe it was some kind of special one-off project at Google. Once I stumbled onto Angular Material I sort of forgot about Polymer because I didn't have a dedicated UI guy, and there was a nice cache of controls to…

Some potentially relevant links for you...

1: https://beta.webcomponents.org/ - A public repository of web components (including the official Polymer components and community components).

2: https://polymer-slack.herokuapp.com/ - Join the Polymer community on Slack. All of the core team members are there as well :)

Re: An Introduction to Polymer - A Web Component Library

#22

Post by spankalee »

adamduren wrote: post #14

I found Polymer to be very easy to pickup coming from Angular 1 & 2. The only friction I experienced was difficulty integrating TypeScript. Given how Polymer components are typically written with the JavaScript included with the HTML file of the component this was not really an easy option for a beginner. However using tools like polymer-build with gulp you can still get TypeScript support. In the upcoming Polymer 2.…

Yep, we're going to greatly expand our support of TypeScript with Polymer 2.0. We'll have supported type declarations, and decorators to help write elements, and eventually (though maybe not at Polymer 2.0's release) tools support in the Polymer Analyzer and IDE plugins. You'll even be able to type check and auto-complete in your templates.

There's a little dated PR that adds TypeScript decorators here: https://github.com/Polymer/polymer/pull/3954 We're probably going to break out the decorators into a separate packages, since the ECMAScript decorators proposal has diverged a bit from what TypeScript supports now.

Re: An Introduction to Polymer - A Web Component Library

#23

Post by hanspragt »

I have recently decided to switch from Polymer to Material2 for the following reasons:

- Polymer is only available through bower, which means I have to teach 2 package management systems to my developers.

- The documentation is not great (for instance, events are documented in camelCase, but must be listened for in Angular 2 using dashes-between-words).

- There are serious issues [0] which not gone resolved for a long time.

- The behavior of important components is not intuitive. For instance, the menu component acts more like a list which has a selected item (which also cannot be reselected)

[0]: https://github.com/webcomponents/webcomponentsjs/issues/541

Re: An Introduction to Polymer - A Web Component Library

#24

Post by adamduren »

hanspragt wrote: post #23

I have recently decided to switch from Polymer to Material2 for the following reasons: - Polymer is only available through bower, which means I have to teach 2 package management systems to my developers. - The documentation is not great (for instance, events are documented in camelCase, but must be listened for in Angular 2 using dashes-between-words). - There are serious issues [0] which not gone resolved for a lon…

I think you meant to say that you switched to Angular 2 with Angular Material 2 which still considers itself in alpha status which I would not currently use in production.

I agree that the documentation can be improved in that respect, however once you have learned the convention it applies for all components. In angular 1 documentation you had the same issues of `ngRepeat` and similar directives being expressed as `ng-repeat` in the HTML attributes. The only explanation is in the directive documentation [0] which can be pretty exhausting to take in.

[0]: https://docs.angularjs.org/guide/directive#normalization

Re: An Introduction to Polymer - A Web Component Library

#26

Post by hanspragt »

adamduren wrote: post #24
hanspragt wrote: post #23

I have recently decided to switch from Polymer to Material2 for the following reasons: - Polymer is only available through bower, which means I have to teach 2 package management systems to my developers. - The documentation is not great (for instance, events are documented in camelCase, but must be listened for in Angular 2 using dashes-between-words). - There are serious issues [0] which not gone resolved for a lon…

I think you meant to say that you switched to Angular 2 with Angular Material 2 which still considers itself in alpha status which I would not currently use in production. I agree that the documentation can be improved in that respect, however once you have learned the convention it applies for all components. In angular 1 documentation you had the same issues of `ngRepeat` and similar directives being expressed as `…

No, we used Polymer in an Angular 2 app. Even though Material 2 is in alpha, the components we need just work better than in Polymer; They have fewer quirks, fewer bugs, and fit better into the Angular 2 ecosystem.

Re: An Introduction to Polymer - A Web Component Library

#27

Post by adamduren »

hanspragt wrote: post #26
adamduren wrote: post #24

Earlier quoted context omitted.

I think you meant to say that you switched to Angular 2 with Angular Material 2 which still considers itself in alpha status which I would not currently use in production. I agree that the documentation can be improved in that respect, however once you have learned the convention it applies for all components. In angular 1 documentation you had the same issues of `ngRepeat` and similar directives being expressed as `…

No, we used Polymer in an Angular 2 app. Even though Material 2 is in alpha, the components we need just work better than in Polymer; They have fewer quirks, fewer bugs, and fit better into the Angular 2 ecosystem.

Ah, I understand now. I've done some work integrating Angular 2 and Polymer and there are pitfalls.

I've come across this repo in the past for integrating the two but I personally haven't used it yet.

https://github.com/vaadin/angular2-polymer

Re: An Introduction to Polymer - A Web Component Library

#29

Post by ergo14 »

Pigo wrote: post #19
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…

I first looked at Polymer quite awhile ago, maybe over a year. I guess I kind of thought it was a stepping stone to Angular 2 which uses a component model, like most of the other latest frameworks. Or that maybe it was some kind of special one-off project at Google. Once I stumbled onto Angular Material I sort of forgot about Polymer because I didn't have a dedicated UI guy, and there was a nice cache of controls to…

> Once I stumbled onto Angular Material I sort of forgot about Polymer because I didn't have a dedicated UI guy

That is kind of funny - because it looks like polymer has much more complete Material UI implementation compared to both Angulars (unless they catched up on that).

Re: An Introduction to Polymer - A Web Component Library

#30

Post by ergo14 »

hanspragt wrote: post #23

I have recently decided to switch from Polymer to Material2 for the following reasons: - Polymer is only available through bower, which means I have to teach 2 package management systems to my developers. - The documentation is not great (for instance, events are documented in camelCase, but must be listened for in Angular 2 using dashes-between-words). - There are serious issues [0] which not gone resolved for a lon…

Polymer 2.x will be distributed with npm + yarn. They had technical reasons to stick with bower for time being. They worked with yarn and it is the solution to the problem :-) There was a talk on the subject on polymer summit.
Post reply on HN