Asteroid is indeed pretty cool, I’ve also used it before. I’ve used a pure Polymer frontend, since I prefer the component model of Polymer to Blaze templates.
But then I found myself a bit isolated from the packages on Atmosphere. Not wanting to implement a lot of logic that already existed as Atmosphere packages, I changed to Meteor. To stay as backend agnostic as possible, I put all my Polymer code simply in the public/ folder and used the public APIs exposed by Meteor to the client. But then again for using custom build tools for Polymer I need to write integrations into the Meteor world and I actually wish I would have stayed with Asteroid.
But why do I need to be in this situation anyway? According to the Meteor website the Meteor platform is just a recommended stack, consisting of all the core parts of Meteor. Why isn’t it possible to just use the DDP implementation and mini-mongo on a client app? As I read on the website this should be possible sometime. In the Trello roadmap I can not find something about this.
Does somebody know if there is an interest of the Meteor team to go into that direction or will it always be that other libraries/frameworks/tools have to integrate into Meteor and not the other way round?