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

[whatwg] [canvas] request for {create, get, put}ImageDataHD and ctx.backingStorePixelRatio

From: Oliver Hunt <oliver@apple.com>
Date: Mon, 16 Apr 2012 14:06:53 -0700
Message-ID: <7190CDD7-3670-4585-BA71-990D277CD4A9@apple.com>

On Apr 16, 2012, at 2:00 PM, Darin Fisher <darin at chromium.org> wrote:
> I have learned that it is not commonly accepted that reading ImageData can be slow.  I had assumed otherwise.

Yes, it's possible to make reading image data slow, but i can make _anything_ slow.  I could make postMessage slow even though it's ostensibly asynchronous simply by triggering a copy of a large enough object.

The problem I have is that there has been any demonstration that making the data read asynchronous will save substantial time vs. a) the typical operations that will subsequently be performed on the retrieved data or b) that it would generally take longer than a runloop cycle.

Knowingly adding complexity without any good metrics that show getImageData{HD} is sufficiently expensive to warrant that complexity seems like the wrong path to take.

> 
> -Darin
Received on Monday, 16 April 2012 14:06:53 GMT

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