On 25/10/2013, at 08:17, Ilya Grigorik wrote:
With HTTP 1.x (and without sharding) you can fetch up to six resources in
parallel. With HTTP 2.0, you can fetch as many resources as you wish in
parallel. The only reason bundling exists as an optimization is to work
around the limit of six
Tristan Zajonc mailto:tris...@senseplatform.com
October 27, 2013 5:47 PM
I apologize for jumping in here with an incomplete understanding
what's being proposed, but perhaps somebody can help clarify it for
me. I've been following value types and operator overloading
discussion with great
Brendan Eich wrote:
The API Function.defineOperator(symbol, type1, type2) would be
perfect to support this. However I assume this is not the intention?
Is there any openness to supporting user defined infix operators or
at least an extended set similar to Python's PEP 225 proposal
As far as I can tell, the two places in ES5 that test [[Class]] being
equal to Array are Array.isArray() and Array.prototype.concat.
In ES6, the former does some sort of brand check, but the latter calls
IsConcatSpreadable, which checks for a @@isConcatSpreadable symbol.
It seems to me like
On Mon, Oct 28, 2013 at 8:14 AM, Brendan Eich bren...@mozilla.com wrote:
Tristan Zajonc mailto:tristan@senseplatform.**comtris...@senseplatform.com
October 27, 2013 5:47 PM
I apologize for jumping in here with an incomplete understanding what's
being proposed, but perhaps somebody can help
Tristan Zajonc wrote:
Having === be reference equality is fine if that's a hard JS
requirement. For a matrix API, there is some flexibility on
comparison operators, but transient value comparison returning a
single boolean is the most natural, other issues aside. I'm not sure I
fully
On Mon, Oct 28, 2013 at 8:20 PM, Boris Zbarsky bzbar...@mit.edu wrote:
In terms of existing ArrayClass objects that are shipping on the web right
now, Gecko is shipping (though perhaps not in final releases yet) the .ports
of a MessageEvent and the return value of getClientRects(). I _think_
On 10/28/13 7:13 PM, Anne van Kesteren wrote:
On Mon, Oct 28, 2013 at 8:20 PM, Boris Zbarsky bzbar...@mit.edu wrote:
In terms of existing ArrayClass objects that are shipping on the web right
now, Gecko is shipping (though perhaps not in final releases yet) the .ports
of a MessageEvent and the
On 10/28/13 7:43 PM, Boris Zbarsky wrote:
Our current implementation returns vanilla JS arrays, but returns a
new one every get, which is pretty suboptimal. So we were considering
changing them to some ArrayClass interface and thinking about what
issues that might cause for callers...
To be
On 10/28/13 7:43 PM, Boris Zbarsky wrote:
Our current implementation returns vanilla JS arrays, but returns a
new one every get, which is pretty suboptimal. So we were considering
changing them to some ArrayClass interface and thinking about what
issues that might cause for callers...
To be
On Mon, Oct 28, 2013 at 4:13 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Oct 28, 2013 at 8:20 PM, Boris Zbarsky bzbar...@mit.edu wrote:
In terms of existing ArrayClass objects that are shipping on the web right
now, Gecko is shipping (though perhaps not in final releases yet) the
On Oct 28, 2013, at 4:43 PM, Boris Zbarsky wrote:
...
This came up today in a discussion of how we want to implement
https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html in Gecko, and
specifically how to implement the axes and buttons attributes on
From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of Allen
I don't think there is any thing wrong with using Object.freeze if you really
need to return an immutable object. But what's wrong with returning a fresh
object each time? Are these operations highly likely to be used
On Oct 28, 2013, at 5:25 PM, Domenic Denicola wrote:
I think the issue is that these things are properties, either because of web
legacy (as in some specifications) or because the spec writers conceptualize
them as such and are reluctant to change them (for the newer specifications).
And
From: Allen Wirfs-Brock [mailto:al...@wirfs-brock.com]
So what's so onerous about returning a fresh array from the getter each time
it was called.
The fact that `api.property !== api.property`.
___
es-discuss mailing list
es-discuss@mozilla.org
On Oct 28, 2013, at 5:52 PM, Domenic Denicola wrote:
From: Allen Wirfs-Brock [mailto:al...@wirfs-brock.com]
So what's so onerous about returning a fresh array from the getter each time
it was called.
The fact that `api.property !== api.property`.
You mean people want to do identity
16 matches
Mail list logo
