On Jul 7, 2015, at 3:36 AM, Yusuke SUZUKI utatane@gmail.com wrote:
On Tue, Jul 7, 2015 at 8:54 AM, Geoffrey Garen gga...@apple.com
mailto:gga...@apple.com wrote:
I’m suggesting a default runloop for non-web content.
I haven’t read through the details of integrating with the web
On Wed, Jul 8, 2015 at 4:07 AM, Maciej Stachowiak m...@apple.com wrote:
On Jul 7, 2015, at 3:36 AM, Yusuke SUZUKI utatane@gmail.com wrote:
On Tue, Jul 7, 2015 at 8:54 AM, Geoffrey Garen gga...@apple.com wrote:
I’m suggesting a default runloop for non-web content.
I haven’t read
On Tue, Jul 7, 2015 at 8:54 AM, Geoffrey Garen gga...@apple.com wrote:
I’m suggesting a default runloop for non-web content.
I haven’t read through the details of integrating with the web content
definition of micro task.
Geoff
OK. Reinventing runloop each time is costly.
On the other
I’m suggesting a default runloop for non-web content.
I haven’t read through the details of integrating with the web content
definition of micro task.
Geoff
On Jul 6, 2015, at 4:44 PM, Maciej Stachowiak m...@apple.com wrote:
Should JS be defining an event loop abstraction that WebCore
Should JS be defining an event loop abstraction that WebCore then uses? That
would be weird, because the required behavior of the even loop in web content
is chock full of issues that are not at all related to JavaScript. JSC doesn't
even know enough to run microtasks at all the right times
I think it would be better for JavaScriptCore to handle micro tasks natively.
It’s not so great for each client to need to reinvent the microtask runloop
abstraction.
Geoff
On Jul 6, 2015, at 10:05 AM, Yusuke SUZUKI utatane@gmail.com wrote:
Hi WebKittens,
I've landed the update of
6 matches
Mail list logo
