[whatwg] new constructor method for Path2D

Joe Gregorio jcgregorio at google.com
Mon Mar 10 11:07:28 PDT 2014

On Mon, Mar 10, 2014 at 2:02 PM, Rik Cabanier <cabanier at 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
at up to 60fps?

More information about the whatwg mailing list