New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
measure polymer-interop overhead #19743
Labels
Comments
Removed this from the 1.6 milestone. |
Removed Polymer-P-1 label. |
Added PolymerMilestone-Next label. |
Removed Polymer-Milestone-Next label. |
This was referenced Jun 5, 2015
This issue has been moved to dart-archive/polymer-dart#223. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need some benchmarks to know what's the impact of using a polymer.js element from Dart vs using a port of the same element.
There is probably value in having some things implemented in Dart, but there are probably many cases where it doesn't matter that a custom-element is running in JS.
The text was updated successfully, but these errors were encountered: