2 ms·
It was introduced because "web developers are building more sophisticated applications where application performance is increasingly important. Developers need
by niftich 9y ago
It was introduced because "web developers are building more sophisticated applications where application performance is increasingly important. Developers need the ability to assess and understand the performance characteristics of their applications using well-defined interoperable measures." [1].
Browser-engine makers, like WebKit, were itching [2] to implement this, so they participated early on.
The proceedings of this W3C working group were conducted in the open; their mailing list archive is public [3].
For a cute and oblivious early message, see this post [4] from July 2010. Luckily it was eventually followed up by the first wave of enumerated privacy concerns [5] in October 2010.
[1] https://lists.w3.org/Archives/Public/public-web-perf/2010Jun/att-0002/webperf.html https://lists.w3.org/Archives/Public/public-web-perf/2010Jun... [2] https://lists.w3.org/Archives/Public/public-web-perf/2010Jul/0012.html https://lists.w3.org/Archives/Public/public-web-perf/2010Jul... [3] https://lists.w3.org/Archives/Public/public-web-perf/ https://lists.w3.org/Archives/Public/public-web-perf/ [4] https://lists.w3.org/Archives/Public/public-web-perf/2010Jul/0009.html https://lists.w3.org/Archives/Public/public-web-perf/2010Jul... [5] https://lists.w3.org/Archives/Public/public-web-perf/2010Oct/0027.html https://lists.w3.org/Archives/Public/public-web-perf/2010Oct...