+ 1 to François's comments.
You're not saying that gzipping and wise pre-fetching and parallel download
of scripts don't improve page load times. Or are you?
- We already have transfer-encoding in HTTP, and yes, you should definitely
use it!
- Prefetching is also an important optimization, but
Ilya ... just to re-clarify what was the discussion about: Generic Bundling
... not HTTP Bundling.
I don't know why many keep coupling and confining HTML5 over HTTP and
nothing else.
Bundling as you do with executables or apps, bundling as you send a single
file update for your customer to
On 24/10/2013, at 17:06, François REMY wrote:
HTTP 2.0 can send you multiple files in parallel on the same connection: that
way you don't pay (1) the TCP's Slow Start cost, (2) the HTTPS handshake and
(3) the cookie/useragent/... headers cost.
Doesn't connection:keep-alive deal with (1) and
± HTTP 2.0 can send you multiple files in parallel on the same connection:
that
± way you don't pay (1) the TCP's Slow Start cost, (2) the HTTPS handshake and
± (3) the cookie/useragent/... headers cost.
±
± Doesn't connection:keep-alive deal with (1) and (2) nicely?
You still have to pay it 6
Having sort keys in the collator would allow user to be more flexible in
comparing strings, but your* approach is good enough for now.
* toUpperCase spec as it stands
2013/10/24 Mihai Niță mn...@google.com
Does this sufficiently cover the locale independent case folding use
case?
I think it
On Fri, Oct 25, 2013 at 3:53 AM, François REMY
francois.remy@outlook.com wrote:
± 4.- It's not http2.0 *or* .zip bundling. We could have both. Why not?
Because using a ZIP file is a bad practice we certainly should not allow. As
stated before, it will make the website slow [...]
It seems
On Thu, Oct 24, 2013 at 7:38 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Oct 24, 2013 at 3:31 PM, Mathias Bynens math...@qiwi.be wrote:
Imagine you’re writing a JavaScript library that escapes a given string as
an HTML character reference, or as a CSS identifier, or anything else. In
ES5 introduced several rules regarding duplicate in property definitions in an
object literal. The rules are roughly:
You can use the same property name in both a data property definition and
an accessor property definition
You can't define more than one get accessor for a given
On Fri, Oct 25, 2013 at 12:17 AM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
Ilya ... just to re-clarify what was the discussion about: Generic
Bundling ... not HTTP Bundling.
I don't know why many keep coupling and confining HTML5 over HTTP and
nothing else.
Bundling as you do
On Fri, Oct 25, 2013 at 6:24 AM, Jonathan Bond-Caron
jbo...@gdesolutions.com wrote:
On Wed Oct 23 10:17 PM, Ilya Grigorik wrote:
In short, pitching zip bundling as a performance optimization is a
complete misnomer. If anything, it will only make things worse, even
for HTTP 1.x clients.
I know we would like people to stop using the Arguments object, but just to be
sure, is it intentional that the Arguments Object does not have an @@iterator ?
—Oliver
___
es-discuss mailing list
es-discuss@mozilla.org
I asked about this several months back[1]. There is a bug filed
https://bugs.ecmascript.org/show_bug.cgi?id=1114
Nathan
[1] https://mail.mozilla.org/pipermail/es-discuss/2012-December/027372.html
From: oli...@apple.com
Subject: Iteration of the
12 matches
Mail list logo
