We're still developing Polymer 2 applications but considering the move. However there's one big questions that comes up. What to do with third-party components that still rely on Polymer 2? I know there's the Polymer Modularizer but shall we really convert third-party code so that it works in our newly ported Polymer 3 apps? That doesn't feel very good as you suddenly end up with maintaining foreign code and have to look after updates and fixes for those components yourself.
There are piles of good components around at webcomponents.org which are still in Polymer 2 and you never know if they will ever be ported to Polymer 3. Are there alternatives to the conversion? Another worry: what happens with the next major update? Will we need to port all our our components (which are certainly hundreds already) with every new major release? That really puts a huge burden on developers (and project leads looking for the budget). I understand that the standard itself is still moving but these questions should be considered before such breaking changes are set in place. Thanks for your thoughts on this, Joern Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/5bd2ca90-6d23-49cc-8e23-7d4643b0b30d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
