Re: [whatwg] Deferring javascript download and execution until after onload

2012-12-08 Thread Kyle Simpson
Further evidence that the current state of the web is not friendly with respect to how browsers default to treating script loading/parsing/executing. https://www.facebook.com/notes/facebook-engineering/under-the-hood-the-javascript-sdk-truly-asynchronous-loading/10151176218703920 The efforts tha

Re: [whatwg] Deferring javascript download and execution until after onload

2012-11-28 Thread Kyle Simpson
Ian, > The only cost there could be is the cost > of executing the script, and it's already trivial to offload that: just > put all the code in a function, then call the function when you're ready. > It's already possible now to design scripts such that they don't run until > you call them, so

Re: [whatwg] Deferring javascript download and execution until after onload

2012-11-28 Thread Kyle Simpson
Ian, > The cost of parsing the script can be done async, even off the main thread > in theory, so it's a non-issue. You have asserted many times that parsing is off the main thread, therefore it doesn't matter. That makes the giant (and I think faulty) assumption that the device in question ha