Re: Safe, Closure-free, Serializable functions‏

2013-09-26 Thread David Herman
On Sep 26, 2013, at 1:10 PM, François REMY wrote: >>> TLDR ==> The web needs a way to express executable code that does not rely >>> on its parent context, is guaranteed to be side-effect-free, and can be >>> executed safely anywhere (even in a different thread/worker/window/device, >>> or as

RE: Safe, Closure-free, Serializable functions‏

2013-09-26 Thread François REMY
>> TLDR ==> The web needs a way to express executable code that does not rely >> on its parent context, is guaranteed to be side-effect-free, and can be >> executed safely anywhere (even in a different thread/worker/window/device, >> or as callback for browser code being executed while the DOM i

Re: Safe, Closure-free, Serializable functions‏

2013-09-26 Thread Mike Samuel
2013/9/26 David Bruant : > Le 26/09/2013 01:29, François REMY a écrit : > >> Hi, >> >> TLDR ==> The web needs a way to express executable code that does not rely >> on its parent context, is guaranteed to be side-effect-free, and can be >> executed safely anywhere (even in a different thread/worker

Re: Safe, Closure-free, Serializable functions‏

2013-09-26 Thread David Bruant
Le 26/09/2013 01:29, François REMY a écrit : Hi, TLDR ==> The web needs a way to express executable code that does not rely on its parent context, is guaranteed to be side-effect-free, and can be executed safely anywhere (even in a different thread/worker/window/device, or as callback for bro

Safe, Closure-free, Serializable functions‏

2013-09-25 Thread François REMY
Hi, TLDR ==> The web needs a way to express executable code that does not rely on its parent context, is guaranteed to be side-effect-free, and can be executed safely anywhere (even in a different thread/worker/window/device, or as callback for browser code being executed while the DOM is not r