

We are using GPUs to render polygonalized shapes where available, though that has some accuracy issues with stroke scaling. (Ruffle is all people working spare-time currently) The performance ceiling with Rust is way higher than JavaScript, but we're nowhere near that yet, much yet at the point where we'd have to start writing JIT compilers for AS2 or AS3. Shumway used to be a Mozilla project with corporate backing that would explain why their implementation was so complete. For example, after figuring out how DisplayObjectContainer IDs and timeline depths interact, Toad06 and I went through several rounds of regression testing with AVM1 content because of how foundational the changes were. Adding AS3 support also means making sure we can leverage the same object hierarchy without breaking any of those fixes. Most of our effort has gone into finding and implementing the bottomless pit of strangeness that is AVM1 and it's execution model. DisplayObjectContainer support just landed a few days ago, but yes, our AS3 support is basically nothing right now.
