W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2012

[whatwg] API for encoding/decoding ArrayBuffers into text

From: Jonas Sicking <jonas@sicking.cc>
Date: Sun, 1 Apr 2012 15:28:19 -0700
Message-ID: <CA+c2ei9caFqRHFt4DT-2xW=LYETgfjNCKtf6A8s1x0iUER+sTg@mail.gmail.com>
On Sat, Mar 31, 2012 at 6:13 PM, Glenn Maynard <glenn at zewt.org> wrote:
> On Wed, Mar 28, 2012 at 1:44 AM, Jonas Sicking <jonas at sicking.cc> wrote:
>>
>> Scanning over the buffer twice will cause a lot more memory IO and
>> will definitely be slower.
>
> That's what cache is for.? But: benchmarks...
>
>> We can argue weather it's meaningfully slower or harder. But it seems
>> like we agree that it's slower and harder.

I'm saying that if an API is better in every way then it doesn't seem
like an interesting discussion how much better, we should clearly go
with that API.

/ Jonas
Received on Sunday, 1 April 2012 15:28:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:07 GMT