+public-script-coord
-public-webapps
(Soon I will start dropping es-discuss too).
On Sep 29, 2009, at 3:38 AM, Yehuda Katz wrote:
I meant "actually written". Being able to see actual code that
implemented pieces of the IDL in ES would make some of the more
complex interactions more obvious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just FYI, there has also been significant discussion on CommonJS
regarding the use promises [1] and concurrency [2] in JavaScript,
CommonJS is focused on standardizing library APIs for JavaScript, in
particular on the server. Obviously on the server t
Brendan Eich wrote:
> Beyond this, concurrency via workers is great for certain use-cases but
> not enough for others.
>
> In TC39 we are talking about formalizing the run-to-completion execution
> model of JS, along with asynchronous message passing concurrency. In
> particular, we're looking at
+public-script-coord
On Sep 27, 2009, at 4:19 PM, David-Sarah Hopwood wrote:
Maciej Stachowiak wrote:
On Sep 27, 2009, at 11:14 AM, Brendan Eich wrote:
On Sep 27, 2009, at 10:41 AM, David-Sarah Hopwood wrote:
That can already be done in ES5. As I've previously suggested:
function Date(yea
I meant "actually written". Being able to see actual code that implemented
pieces of the IDL in ES would make some of the more complex interactions
more obvious (I suspect).
-- Yehuda
On Tue, Sep 29, 2009 at 3:28 AM, Maciej Stachowiak wrote:
>
> On Sep 28, 2009, at 11:34 PM, Yehuda Katz wrote:
>
On Sep 28, 2009, at 11:34 PM, Yehuda Katz wrote:
It would be pretty nice if the language bindings of WebIDL were
available in pure ES, where possible. To some degree, that is not
currently possible (in ES3), but it will be a lot better in ES5. I
think it might actually be possible to get a larg
6 matches
Mail list logo
