In my Paper project I have some layers with a large number of Paths (ex: layer 2 below). If I move around the paths in layer 1, the rendering is quite slow. Due to the separation of the layers, I would expect Layer 1 to be unaffected by the number of paths in Layer 2.
In the short-term I have reduced the severity of the issue by rasterizing Layer 2 while dragging Layer 1. However, this still presents a poor user experience due to the time it takes to rasterize Layer 2, and has resulted in a lot of complex and unmaintainable code in our codebase.
I am wondering if it is possible to optimize Paper JS in a way that manipulating Layer 1 can happen quickly (regardless of the number of paths in Layer 2) without needing to rasterize Layer 2.
I'm not sure if this is the right forum to mention this, but since this behavior is important to my project, I'm willing to donate meaningfully to Paper JS in order to prioritize this issue.