Hey,
If you did not know, turbowarp is a Scratch mod that runs projects several times faster than Scratch using a compiler.

A few days ago, I ask myself why Turbowarp is so fast and why couldn't Scratch just use the same method as Turbowarp to make Scratch as fast. I ask a few people if they knew the answer and they told me that this could not be possible because you can not edit running scripts on turbowarp. Since editing running scripts is a very important part of Scratch, it's understandable that the Scratch Team aren't going to give up this ability for the sake of a compiler.

But I'm thinking that they could use a compiler like turbowarp, but only for the project page. So, the editor would stay the same, but when you would go on the project page, it would use a compiler to make the project run many times faster. This way, you would still be able to edit running scripts in the editor, but you would benefit from the compiler's performance boost when playing/viewing the project on the project page.

Since both pages would be capped at 30 fps, the speed on both would be the same. The difference would only be noticeable when the normal scratch would reach its limit. I feel like most people who have reached this limit would appreciate if their projects would run faster even if it’s only on the project page.

I seriously think that this could improve Scratch.


Here are the pros:

1. Better performance

- Weaker School computers would stop lagging which would make Scratch accessible to more Scratchers.

- Projects with a large number of costumes such as MAPs could be played without any lag (currently a lot of MAPs can't be watched on Scratch because of how laggy they are)

- We could double the clone number limit which could lead to an infinite amount of possibilities!

- Pen projects would be way faster and we could maybe improve the pen resolution (Its resolution is currently really
low)

- (optional) The Scratch Team could add a 60 FPS option to make project run smoother with the added
performance without any lag.

- Scratch would not crash as often when vewing/playing animations or complex games.

- The added performace would be welcomed for experienced Scratchers but would be as welcomed by
less experienced Scratchers who would be able to play more complex and fun games and be inspired
by Scratch's potential.


Here are the cons:

- I’m not sure if it would be possible to switch between the project page and the editor without it stopping the project.



I'm an not a dev so tell me if something do not make sense in what I just said, but I seriously think that this could be an remarkable update to Scratch that could be extremely useful for both experienced Scratchers and less experienced Scratchers!

What do you think?

support! anything to make projects run faster is a good idea in my opinion.
however, I feel that there might be issues implementing this, having two different project runners can be hard to implement.

Yes this will be very useful not only for weaker school computers but weaker computers, laptops and tablets as well.

Support. No more lag on huge projects. Yay

Honestly, I would absolutely love this for my school computer. Some projects just completely lag out on it.

I support this, it would be useful for people with slower computers and I don't see why they couldn't implement it when they had two different project viewers in the 1.4 or 2.0 days. (normal and experimental)

support! in my featured game Choo-Choo Chaos, it lags sometimes due to the number of broadcasts being broadcasted. this would totally fix!

Not gonna lie, this is gonna save me a lot of ram while playing scratch projects or in the editor but there should be a way to disable the compiler and should be off by default for already existing projects.

randomguy3513 wrote:

Not gonna lie, this is gonna save me a lot of ram while playing scratch projects or in the editor but there should be a way to disable the compiler and should be off by default for already existing projects.

I agree, it's definitely not common for a project to break because of it but it should still be an option, just in case.

-Valtren- wrote:

support! anything to make projects run faster is a good idea in my opinion.
however, I feel that there might be issues implementing this, having two different project runners can be hard to implement.

I agree, the most important thing would be to make sure that projects works exactly the same both on the editor and on the project page with the compiler. Turbowarp seems to be doing an very good job at this so I think it could be possible.

Support! This would reduce lag in huge projects.

Full support. I'd much rather have this than having to put a TurboWarp link in the instructions and hoping people actually click on it to properly play the project.

I support. 3rd party compilers don't typically have user authentication, so laggy projects cannot have verifiable cloud highscores.

Doesn't turbowarp compile scratch to javascript and then run the javascript instead or something?
while scratch runs a program that reads and runs the scratch program, and having a program run a program which runs a program is definitly slower then just running a program

blablablahello wrote:

Doesn't turbowarp compile scratch to javascript and then run the javascript instead or something?
while scratch runs a program that reads and runs the scratch program, and having a program run a program which runs a program is definitly slower then just running a program

Yes, that is why Turbowarp is so much faster than Scratch.

MeIzAwezomeDede wrote:

Full support. I'd much rather have this than having to put a TurboWarp link in the instructions and hoping people actually click on it to properly play the project.

Yes and a lot of new scratchers don’t know what turbowarp is and they often think that it’s just turbo mode. It would be simpler if we did not have to use a different site to run games/animations without any lag.

Sure I guess, but at the same time it might make other parts of scratch more complicated, and would take a while to do, this might change how coding works on scratch, but otherwise support.

Increasing the clone limit is rejected yk

QuantumScratcher wrote:

Increasing the clone limit is rejected yk

That isn't what they're suggesting. What they're suggesting may lead to the clone limit being able to be raised, but that isn't the main focal point of their suggestion.

musicROCKS013 wrote:

QuantumScratcher wrote:

Increasing the clone limit is rejected yk

That isn't what they're suggesting. What they're suggesting may lead to the clone limit being able to be raised, but that isn't the main focal point of their suggestion.

Thank you, yes, increasing the clone limit is rejected because of Scratch’s current performance, but if projects were to run many times faster on the project page with a compiler, I think we could consider increasing the limit by a few hundreds