Am I reading this right? Are you actually saying ExplorerCanvas (canvas on top of VML) is faster than native canvas in firefox, webkit, etc? I have some exper

Am I reading this right? Are you actually saying ExplorerCanvas (canvas on top of VML) is faster than native canvas in firefox, webkit, etc? I have some experience with this -- my site uses canvas / ExplorerCanvas quite a lot -- ExplorerCanvas is both buggy and extremely slow for any kind of animation. Particularly long running animation (as in games). I wish it wasn't so. VML may or may not perform well, but it's a different kind of api than canvas. In VML, like SVG, you're intended to draw a bunch of shapes and then manipulate them. To animate a circle crossing the screen, you draw the circle and the move it every tick. The library manages the redraws, etc. With canvas, you redraw every frame. So, to animate that circle you draw it in a different position every tick. If you run canvas on top of VML you end up redrawing a lot of extra elements which get reinserted into the dom at every step. They're just fundamentally different approaches and the impedance mismatch kills ExplorerCanvas's performance. If this has changed recently, btw, I'd love to hear about it!