RE: setImmediate usage on the web

Although I agree the name is suboptimal, 5% real-world web usage in Microsoft Edge is quite high usage to consider renaming or removing an existing API. 5% real-world usage hints that there is some demand for the functionality the API provides even though it is only implemented in 1 browser.

Can you please elaborate on the ES6/7 feature that has the low priority callback characteristic of setImmediate?


From: Hiroshi Kawada []
Sent: Wednesday, June 24, 2015 12:09 AM
To: Todd Reifsteck
Subject: Re: setImmediate usage on the web

I think setImmediate is too vague. Web developers just make callback executing after I/O(Layout/Rendering) or waiting for that thread gets idle. Some ES6 features that new browsers are already supported and requestAnimationFrame API covers this use case.

So, we need to choose these 3 idea :

1. rename setImmediate to setIdleTask ... separate out two use cases(requestAnimationFrame and setIdleTask).
2. remove this spec. ... ES6/7 will cover this use case.
3. keep on this spec ... waiting for other idea or usage.

On Tue, Jun 23, 2015 at 3:34 AM, Todd Reifsteck <<>> wrote:
I promised a few weeks ago to come back to the Web Performance Group with data on setImmediate usage within Microsoft Edge. Upon examining the data, I found that it required more parsing and analysis because the usage was much higher than I expected. What I discovered was that the usage was much higher in scenarios where setImmediate was guaranteed to be available such as Windows Store applications.

% of Navigations that include a usage of setImmediate

•         Microsoft Edge browser navigations—4.73%

•         All instances of edgehtml.dll (including apps)—21.88%


KAWADA Hiroshi
Web Developer (JPN)

Received on Wednesday, 24 June 2015 08:29:16 UTC