4 ms·

Congrats! So what do you think? About using Polymer I mean. :) Would love to get some insight as to how the experience was learning and building something in

• caleblloyd 10y ago
  Web Components: I think that web components are absolutely the best way to program a web application. Keeping the CSS, HTML, and JavaScript within the boundaries of a component works wonders for organization. It was such a relief coming from the Angular 1 world I usually work in. Polymer: The polymer elements that Google provides are good. The polymer-cli is fantastic, it just works and I didn't have to configure gulp/grunt/browserify/webpack at all. The project needs no node modules, all dependencies come from bower! Non-google custom elements out there lack robust browser support and I find that I don't trust them out of the box. Ecosystem: support for web components has come a ways in the past couple years but still has a ways to go. Chrome natively supports web components but every other non-blink browser uses polyfills, which slows things down. Firefox and WebKit are implementing part of the web components spec, so hopefully it'll get better soon. It's an exciting technology that is very pleasant to code in. Learning the ropes and building the entire site took 20 hours, most of that was dealing with nitpicky browser support issues with scrolling and animation effects. I hope it continues to gains traction and I would definitely use it again!