> What's wrong with vulcanize (combines all your components into one single html file)? Most of the issues I ran into were relating to inconsistent pathing. It

> What's wrong with vulcanize (combines all your components into one single html file)? Most of the issues I ran into were relating to inconsistent pathing. It was difficult to get every type of thing that could use a path (image tags, css, html inclusions, etc) working in a way that worked at both the path of the component and the newly created path when combined. Perhaps this has changed since the last I used Vulcanize but it was very painful at the time. I also had a hell of a time getting the google maps, and a few other google components, to Vulcanize with the rest of my components but I honestly can't remember the issues now. > Polymer now offers Shared styles, so that you don't have to duplicate your css That's Polymer specific though; is there a way to do that with native web components? I could be missing something but it looks specific to Polymer. Regardless I'm glad this is being addressed to a degree but the solution seemed somewhat unintuitive as it's not using CSS semantics for driving the style. Essentially the majority of projects I work on have developers and designers on them. The designers are usually pretty good with CSS, Illustrator and Photoshop so anything outside of CSS requires quite a bit of learning for them so that's a hill I have to battle with techniques such as these. > Get ready for HTTP2 in a few years. Just like I'm not going to be able to use ES6 for many years I'm not holding my breath here :)