Attendees: dbeam, tbuckley, tjsavage
5 January, 2016
MD Downloads going out in M49
Exploring vulcanization, double-checking its impact
Seems like vulcanization improves performance on Mac but less on Linux
AI: dbeam -- determine whether vulcanize is needed
No updates on history/extensions
AI: dbeam -- check in on history/extensions
MD Settings
Lots of improvements & profiling
Automated performance testing with Chrome running various parts of the Settings page
Node in Chrome
Vulcanize is one of the justifications for node in Chrome
Otherwise only needed for bower & crisper
Mostly solved problem: check in results from a machine that has these tools
Less compelling reason to add node to build toolchain
Waiting to figure out vulcanize story before
Vulcanize bundles
AJ has a demo working
Can sort of roll-your-own today using excludes
Would like to factor out the common dependencies of all MD chrome:// pages
Stopped work on Settings prototype for now
Note: was also an experimental version of Polymer
Been a while since a Polymer release
AI: tjsavage -- check with Kevin to see if Polymer release contains anything Settings would care about
Polymer performance testing