Music Xray is continuing our migration from a jQuery plugin based UI system to a component based UI system. There are many competing frameworks out there including Angular, React, and Riot that help solve the declarative UI problem. We choose polymer for a number of reason. But the biggest reason we chose it, is that it is attempting to be standards based and thus natively supported in browsers. That said, many browsers have not fully implemented the web components specification leading to slow performance on browsers yet to update. The end result is that chrome is blazing fast, firefox is a close second, safari can get slow and IE is the worst offender.
Additionally, we are a Rails development shop so we would like our development workflow to function within the context of the asset pipeline as adding an entire frontend toolchain would increase the overall complexity of our build process. This lead us to explore how we can successfully deliver a web component based frontend via the Rails asset pipeline without using tools like vulcanize.
Always concatenate your components
Once you have this in your initializer you will have to clear out your asset cache and clear out any compiled assets you might have lying around.
Restart your webserver and you should be good to go. Please let me know in the comments if this helped you out at all.
My next step is to see if I can get a pull request into the polymer-rails gem with this addition as it would be better to have it all in one spot.