An nameless reader quotes ZDNet:
“One key factor is also whether the respective feature can be turned on by default and thus have maximum impact rather than being only made available optionally,” Sullivan and Ubl stated…. “We want developers to be creative in approaching and solving the performance problem on the web but at a high-level we’ll be looking at features that directly impact loading performance (e.g. use of feature policies, smart bundling, code-splitting, differential serving) and runtime performance (e.g. breaking tasks into smaller, schedulable chunks & keeping fps high)….”
But along with striking up budget to lend a hand frameworks make stronger their codebase, Google has additionally invited the improvement groups a few of these frameworks to offer comments in a extra distinguished position as a part of the Google Chrome building procedure… “Frameworks sometimes make web apps slower. They are also our best hope to make it faster,” a slide in Sullivan and Ubl’s Chrome Dev Summit presentation learn.