Hey Chromium Polymer users!
TLDR: If we want to avoid a 300-500K binary size hit, we need to convert all existing Chromium clients of Polymer over to Polymer 0.8 by the M44 branch date (5/15).
has been released and brought into the Chromium source tree (third_party/polymer/v0_8). With it comes a much smaller binary size, huge performance gains, and JS compiler support. Unfortunately, it also comes with major breaking API changes.
My initial plan was to keep both 0.5 and 0.8 in Chrome until we had fully converted all clients to 0.8 over time. However, I'm already receiving push-back
on having both versions in Chrome's binary at once due to the size overhead. Therefore, our goal will be to convert all existing Polymer clients bundled in Chrome's binary to Polymer 0.8 before the M44 branch point (5/15). This will allow us to avoid having both versions of the library in the Chrome binary in the same release.
I realize that the effort involved in this conversion will be non-trivial for many projects. I (along with other members of the md-settings project) am happy to help any way I can throughout this conversion process through questions, reviews, etc. This mailing list (chromium-polymer) will also be a good place to send questions you have about upgrading. I am confident that the benefits of Polymer 0.8 will be worth the pain of this upgrade process.
Please let me know if you have any questions or concerns. If there is absolutely no way your project will be able to make the switch by the branch date, we will need to try to convince the TPMs to accept the substantial bump in binary size for M44. It is in everyone's best interest to avoid that situation, so please let me know as soon as possible if you have serious doubts about your ability to hit this deadline.