-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add instructions to support Angular v.2.2.0
- Loading branch information
Sami Suo-Heikki
committed
Nov 23, 2016
1 parent
a14c421
commit 86632b0
Showing
3 changed files
with
26 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
86632b0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you find that the performance with the full Shadow DOM v0 API was acceptable? I would like to see how https://github.com/vaadin/expense-manager-ng2-demo performs with these changes, but it looks like it hasn't been updated in September. Most likely using these instructions will result in an app that doesn't perform at an acceptable level for production.
86632b0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Splaktar any update on this? Or would you be willing to conduct a study yourself?
86632b0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BorntraegerMarc Given no evidence that performance would be acceptable and knowing the downsides of Shadow DOM v0, I removed Polymer from my applications and moved over to Angular Material2. It's enabled me to use AOT compilation and improve performance quite a bit while using the latest Angular versions.
I'm hoping to give Polymer another shot in v2.0 once HTML Imports are gone and project gets a bit more mature.