decompme
Investigate scratch performance / look into providing options to turn off certain convenience features
I've gotten some recent feedback that editing code on scratches is extremely sluggish to the point of basically being unusable. Once I get permission, I'll share the videos here.
My thoughts are that we should first try to see what's causing the performance issues and either look for ways to just make things more efficient, or at least provide options that can allow users to disable performance-intensive features if they want to. It's probably not likely we'll find any easy performance gains, since we've already tried to optimize the scratch page at least once or twice, but it's at least worth looking at again since it's been a while.
https://cdn.discordapp.com/attachments/815529862604390411/1102844753512497202/screen-recorder-unlimited-2023-05-02-01-24-20_001.mp4
Codemirror text taking a while to render during scrolling and quite sluggish text entry
https://cdn.discordapp.com/attachments/815529862604390411/1102840158077866034/IMG_0742.mov
the same problem but much worse
Do we know which devices these are? We can totally support a less featureful mode for lower end devices e.g. using a standard textarea, there’s just a feature-perf ratio we need to get right
