Turbowarp is a Scratch mod that compiles projects into JavaScript to make them run really fast. So, why doesn't the ST actually implement such a thing? Is it ashamed of using someone else's idea, not aware of it, scarred that Turbowarp creator will get mad, unable to code such a thing, a mix or something else?

Well, a lot of the features in Turbowarp are great. However, I think that the team just wants to use their own editor…? I'm not 100% sure but I think it has to do with the fact that it's not easy to implement a whole new runtime engine.

I think a) it would be related to text-based coding somehow and b) it may end up being a black box creator out of people's projects.
Also, why make their own version since phosphorus, forkphorus, and turbowarp have been already compiling Scratch projects to Javascript for so long?

gosoccerboy5 wrote:

I think a) it would be related to text-based coding somehow and b) it may end up being a black box creator out of people's projects.
Also, why make their own version since phosphorus, forkphorus, and turbowarp have been already compiling Scratch projects to Javascript for so long?

Answer to your question: 1: In order to have more users use Scratch instead of these alternatives, as you can save normally with it.
2: Many Scratchers aren't aware of the existence of all these sites.

How about just a “Turn On JIT Compiler” in the edit menu?

samq64 wrote:

How about just a “Turn On JIT Compiler” in the edit menu?

I am not making a suggestion, just asking why it isn't added.

The Scratch Team doesn't have the ability to maintain TurboWarp without a lot of effort learning how all the code works. Anytime they made an update to Scratch, they would also need to worry about whether it makes a bug TurboWarp functionality also works, so it is important for them to know how to maintain it. Even if they did know how to maintain TurboWarp, it would still add a lot complexity to adding new features.

The Scratch Team also can't just directly add TurboWarp to Scratch because then they would be running code which is made by someone else and technically might not be safe. They need to understand how the code works.

If you think about it, the main benefits of adding TurboWarp to the Scratch website would 1) more people would know about and use TurboWarp, and 2) some time would be saved for people going to the TurboWarp website.

In this case, the difficulty of adding TurboWarp is greater than the convenience of not going to a different website, which is why the Scratch Team is unlikely to add TurboWarp.

Scratch is perfect just the way it is.

Everyone else is making a guess so I guess I will too.

The entire Scratch Team seems to be pulling in the direction of disseminating Scratch. It’s perfect as it is and the only task on every member of the Scratch Team is to make it appealing and acceptable and welcome in all schools, clubs, summer camps, and homes. The only changes that need to be made are to remove features that anyone would find objectionable or add changes that would help with the spread of Scratch (such as adding a donation button).

Turbowarp does not add a marketing value. It’s not something that in line with the Scratch Team’s current goals.

Maybe someday if the pendulum swings the other direction.

Scratch allows you to edit code while it's running, which is a very important feature that isn't available in TurboWarp.

the reason why turbowarp is so fast is because it compiles scratch to javascript, while the normal scratch vm only interprets it.
compiling is faster but also has some downsides, for example that you cant edit a project while its running.
the ability to edit projects while theyre running is very intuitive and one of the biggest reasons why scratch is so easy to use.
and also tbh 99% of projects (especially made by kids at school, scratch's main demographic) run good enough without any problems.

conclusion: making scratch compile js like turbowarp does kinda defeats the purpose of scratch and is useless for 99% of the projects

ofcourse there could be an option to toggle between interpreting and compiling but i think 99% of scratch users dont know the differnce and it would be too complicated for them

Robby_Blue wrote:

the reason why turbowarp is so fast is because it compiles scratch to javascript, while the normal scratch vm only interprets it.
compiling is faster but also has some downsides, for example that you cant edit a project while its running.
the ability to edit projects while theyre running is very intuitive and one of the biggest reasons why scratch is so easy to use.
and also tbh 99% of projects (especially made by kids at school, scratch's main demographic) run good enough without any problems.

conclusion: making scratch compile js like turbowarp does kinda defeats the purpose of scratch and is useless for 99% of the projects

ofcourse there could be an option to toggle between interpreting and compiling but i think 99% of scratch users dont know the differnce and it would be too complicated for them

Ah, I giess you are right…

On turbowarp you can turn a scratch project into a website/app through a zip file made on the turbowarp packager. This is how I compressed one of my projects into a .zip, added to a USB and made copies for my friends. This also makes an editable copy of your project in JavaScript. What's even better is if you update your game, you have a saved copy of the previous version, allowing you to save many versions of a single project without affecting views/likes/remixes on your project!