- From: Joe Gregorio <jcgregorio@google.com>
- Date: Mon, 10 Mar 2014 14:07:28 -0400
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Dirk Schulze <dschulze@adobe.com>, "whatwg@whatwg.org" <whatwg@whatwg.org>
On Mon, Mar 10, 2014 at 2:02 PM, Rik Cabanier <cabanier@gmail.com> wrote: > > > What are you not sure about? > > The current Path2D interface might be unacceptably slow under certain > circumstances and there's currently no way for authors to work around this. > There has to be a hint. If not, I don't see a way that firefox will ship > this. > What part is slow, the decoding and re-encoding, or is just always the encoding step that is slow? I thought the speed of Path2D came from the reuse, that is, that the build cost wasn't a big concern because the speed came from reusing that same object over and over at up to 60fps?
Received on Monday, 10 March 2014 18:08:13 UTC