 Hey there, Polycasters, Rob here. I just wanted to welcome you to this brand new segment we're doing on our show called Ask Polymer. Every other week, we're gonna do this. We're gonna have you send in questions on a social network of your choosing. You got some sort of crazy earworm, something you wanna know about Polymer, but you're not quite sure about. You send those in, you hashtag it, Ask Polymer, and we will answer it. All right, question number one comes from Kenneth, who writes in and asks, didn't you mention that they would be a CD-in for Polymer or something like that? Is that gonna be rolling out anytime soon? Now, in the past, we've actually encouraged people not to use CD-ins with HTML imports because they would have a hard time deduplicating their dependencies. If they're all coming from different domains, the dedupping mechanism can't really figure out where there are copies of things. But at the recent Polymer Summit, we showed off a new project we've been working on called PolyGit. Adi Osmani did an entire talk where he included PolyGit as one of the segments in there showing how you could use it in your projects. The idea with PolyGit is that it's actually kind of our own magic server. It uses the GitHub, the raw GitHub API as kind of a CD-in-like thing. So it's great for experimenting, not quite ready for production though. You don't wanna be taking PolyGit and using it in a real project. But if you're doing something like a JS bin or a little sample, you just wanna show something off or a prototype, it's perfect for that. And we hope, kind of in the long term, that PolyGit will eventually be production ready. So that could be our CD-in solution down the line. So thank you Kenneth for sending that question in. All right, our next question comes from Andrew, who asks, when will Polymer and Angular play nice together? So great question, Andrew. This is actually something a lot of people ask. They wanna know about Polymer and Angular or Polymer and React or some other framework. The main reason why many of those frameworks have a hard time working with Polymer today is that pretty much all of them predate web components. And so they're not quite sure how to work with things like Shadow DOM. Now, once we have Shadow DOM shipping natively everywhere, the story actually gets a little bit better because it hides and it sort of encapsulates a lot of the things that the web components are doing behind the scenes so the frameworks don't need to know about it. But right now we're still in this little in-between place. We've got polyfills for Shadow DOM and that can trip up some of these frameworks. So when we get native Shadow DOM everywhere, things will be a lot better. Also with something like specifically for Angular and Angular 2, they've been rewriting their data binding systems. It'll work better with the sort of events that Polymer elements fire and they'll also be able to handle Shadow DOM better. They've got a whole sort of Shadow DOM renderer that they're working on. So thank you, Andrew. Really great question. All right, our next question comes from Rory who asks, what is your favorite custom element? All right, this is a pretty good question. Thank you Rory for sending that in. My favorite custom element is either iron local storage or iron Ajax, which we just did an episode on. So you can actually go back and watch the previous episode of Polycast learn all about how to use that element. And the reason why I like both of these is because they're nice declarative data providers. So I can just sort of wire them up in my application and then persist some data or fetch some data. And I don't have to write like any JavaScript to do that, which I don't know, it just makes it a lot easier for me to build apps. So thank you Rory, really great question. Our next question comes from Andre who asks, why did Polymer choose to use Bower as its package manager? And what about something like NPM? Are there plans to switch to that in the future? So great question Andre. The reason why we originally went with Bower is because it gives you this nice flat dependency structure where it installs everything. That's really important for HTML imports. NPM on the other hand tends to nest things that can kind of confuse the system. Now in NPM three, they've done a lot of work to improve on this deduplication mechanism. So now you can get flat directories in NPM three, but the one thing that you can't do is conflict resolution. And that's actually really important for us. We wanna make sure that people aren't installing or getting the wrong version of something and getting some weird errors. So in a future version of NPM, it sounds like they're gonna fix that. And at that point, we'll probably switch over to using that as our package manager. So thank you Andre, really great question. All right, our last question comes from David, who asks, Mozilla has recently said that they're not gonna implement HTML imports instead preferring ES6 modules. So what are your thoughts about that? So great question David. We actually talked about this a little bit at the Polymer Summit. So you check that out over here. And basically the long and short of it is, Mozilla has said that they're not implementing them yet. They didn't say that they're never gonna implement them. And we've been doing a lot of work on the loader spec recently, which is what under the hood, both modules and imports depend upon. And what we'd like to maybe see in the future is perhaps both systems using the same mechanism under the hood. And then you could have modules as the imperative flavor, you could have imports as the declarative flavor and developers could benefit from both. So that is the long-term plan. We're gonna continue working with Mozilla on that to see where we get. So again, thank you David, really great question. Okay, thank you all who sent in those questions. A lot of really great stuff. We didn't get to everything, but we're gonna try to get to them in our future episodes. So be sure to click that little subscribe button down there so you can get notifications as those roll out. If you yourself have questions, you can leave them down in the comments or ping us on a social network of your choosing at hashtag ask polymer. As always, thank you so much for watching and I'll see you next time.