[POSSIBLE SOLUTION?] text-based scratch coding?

7e_x

READ FULL OP BEFORE GIVING YOUR OPINION!
So, as you may have known, text-based Scratch coding has been rejected:

the official list of rejected suggestions wrote:
2.2 Text-based syntax in Scratch
Some users wish to code Scratch not with the blocks, but with typing code instead (similar to how more advanced programming languages work). Others are interested in an option to view, convert, or download Scratch code to other programming languages. However, the Scratch Team has discussed this possibility multiple times and has decided every time that it would not be beneficial for beginners or teachers.

This extends to coding, viewing, converting, or downloading Scratch in any text-based language, including BBCode, Javascript, some form of pseudocode, or some other programming language. If you wish to code using another language, then you can learn it on your own, but it would have to be done outside of Scratch.

Well I have an idea, which could make text-based coding WORK.

So, number 1, DO NOT make it the default option.

Scratch is supposed to be an easy programming language. The main audience is 8-16 year olds, and a kid would get confused if they just saw a weird coding space where you type random stuff. Make it a separate option. Call it “Text Code” and make it a setting. (thank you 7salad3salad)

Number 2, ONLY make it available for Scratchers.

(Some) Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text coding.

Number 3, do NOT make a download to JavaScript or any other language feature.

Scratch is an introductory language. Some people who use Scratch probably don't even know what a “print” is. So, if they check their coding in another language like JavaScript or Lua, they'll probably not even know what it means, and this is just MY theory, but Scratchers might question why it's broken, even though it's literally not. (take this with a grain of salt)

Number 4, use the same naming for the pieces of code as Scratch does.

It takes time to use a text-based programming language, so you can't add another language to Scratch. Use the same names as the blocks does in regular Scratch, so a piece of code looks like this:

when green flag clicked
move (10) steps
say [Meow!] for (2) seconds

This way a Scratcher could get into text coding right away.

So, yeah, that's it for now. Hope the Scratch Team reconsiders this suggestion and might add it in a different way. The end.

Last edited by 7e_x (Jan. 2, 2026 14:10:07)

CodeComet6161

7e_x wrote:
So, number 1, DO NOT make it the default option.

Scratch is supposed to be an easy programming language. The main audience is 8-16 year olds, and a kid would get confused if they just saw a weird coding space where you type random stuff. Make it a separate option. Call it “Text Code” and just put it a button near Code. There, done, easy as that (maybe not, hahaha)

Hmmm

…
This extends to coding, viewing, converting, or downloading Scratch in any text-based language, including BBCode, Javascript, some form of pseudocode, or some other programming language.

Number 2, ONLY make it available for Scratchers.

Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text coding.

That's not always true. Some new scratchers have way more experience than scratchers.

Number 3, do NOT make a download to JavaScript or any other language feature.

Scratch is an introductory language. Some people who use Scratch probably don't even know what a “print” is. So, if they check their coding in another language like JavaScript or Lua, they'll probably not even know what it means, and this is just MY theory, but Scratchers might question why it's broken, even though it's literally not. (take this with a grain of salt)

That's one of the reasons against text code.

7salad3salad

I'm not sure how this solves the problem with it that leads to it being rejected. The primary reasoning appears to be that it would not be beneficial for beginners or teachers, but this hasn't been addressed in the post.

For point one, I think it's reasonable to say it wouldn't be the default option if this gets added. What would be more worrying is a misclick, seeing as you suggest the button be next to “Code”. I think instead of this, it should be locked away as an option under the settings tab, to make it less easy to access and encourage block-based building for beginners who don't quite know their way around the editor yet.

For point two, I think this is solved by my proposed solution for point one. Regardless it only takes 2 weeks minimum to achieve Scratcher rank, and I'm not sure you can advance quick enough to look into text-based coding within this time period (of course unless you're very dedicated and active with using the editor). I think New Scratchers' inability to use cloud variables is more just a spam-prevention thing than an advanced thing.

Point three just seems to be to not add a converter built in, which I do agree with, as this is kind of self-explanatory (and part of the rejection reason itself).

Overall, maybe with a bit of work such a thing could be introduced, but I don't find it all too likely.

Last edited by 7salad3salad (Jan. 1, 2026 21:52:22)

7e_x

CodeComet6161 wrote:
Number 2, ONLY make it available for Scratchers.

Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text coding.
That's not always true. Some new scratchers have way more experience than scratchers.

true, but not all of them do

Number 3, do NOT make a download to JavaScript or any other language feature.

Scratch is an introductory language. Some people who use Scratch probably don't even know what a “print” is. So, if they check their coding in another language like JavaScript or Lua, they'll probably not even know what it means, and this is just MY theory, but Scratchers might question why it's broken, even though it's literally not. (take this with a grain of salt)
That's one of the reasons against text code.

what in mitchel resnicks name do you mean (i know the owner of scratch part is kinda off-topic, but someone please make this a meme)

7e_x

7salad3salad wrote:
I'm not sure how this solves the problem with it that leads to it being rejected. The primary reasoning appears to be that it would not be beneficial for beginners or teachers, but this hasn't been addressed in the post.

For point one, I think it's reasonable to say it wouldn't be the default option if this gets added. What would be more worrying is a misclick, seeing as you suggest the button be next to “Code”. I think instead of this, it should be locked away as an option under the settings tab, to make it less easy to access and encourage block-based building for beginners who don't quite know their way around the editor yet.

true, lemme go change the OP

CodeComet6161

7e_x wrote:
CodeComet6161 wrote:
Number 2, ONLY make it available for Scratchers.

Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text coding.
That's not always true. Some new scratchers have way more experience than scratchers.
true, but not all of them do
Number 3, do NOT make a download to JavaScript or any other language feature.

Scratch is an introductory language. Some people who use Scratch probably don't even know what a “print” is. So, if they check their coding in another language like JavaScript or Lua, they'll probably not even know what it means, and this is just MY theory, but Scratchers might question why it's broken, even though it's literally not. (take this with a grain of salt)
That's one of the reasons against text code.
what in mitchel resnicks name do you mean (i know the owner of scratch part is kinda off-topic, but someone please make this a meme)

not everyone (is not equal to) everyone.
And thinking you're stuck in text code, sounds like a reason to not add text code. Plus:

7salad3salad wrote:
I'm not sure how this solves the problem with it that leads to it being rejected. The primary reasoning appears to be that it would not be beneficial for beginners or teachers, but this hasn't been addressed in the post.

For point one, I think it's reasonable to say it wouldn't be the default option if this gets added. What would be more worrying is a misclick, seeing as you suggest the button be next to “Code”. I think instead of this, it should be locked away as an option under the settings tab, to make it less easy to access and encourage block-based building for beginners who don't quite know their way around the editor yet.

For point two, I think this is solved by my proposed solution for point one. Regardless it only takes 2 weeks minimum to achieve Scratcher rank, and I'm not sure you can advance quick enough to look into text-based coding within this time period (of course unless you're very dedicated and active with using the editor). I think New Scratchers' inability to use cloud variables is more just a spam-prevention thing than an advanced thing.

Point three just seems to be to not add a converter built in, which I do agree with, as this is kind of self-explanatory (and part of the rejection reason itself).

Overall, maybe with a bit of work such a thing could be introduced, but I don't find it all too likely.

7e_x

CodeComet6161 wrote:
not everyone (is not equal to) everyone.
And thinking you're stuck in text code, sounds like a reason to not add text code.

(response to “not everyone (is not equal to) everyone”) im not sure if i understand that, but true, everyone is different
(response to “And thinking you're stuck in text code, sounds like a reason to not add text code.”) i see what you mean. people could just use block coding after all if they're stuck

7e_x

bump

cookedasparagus8

There are many flaws in your argument. Let’s break them down.

7e_x wrote:
Number 2, ONLY make it available for Scratchers.

Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text

So you think once you reach Scratcher status, you have outgrown scratch? There is a reason why the user keeps using Scratch and hasn’t moved on to harder programming languages.

7e_x wrote:
Number 3, do NOT make a download to JavaScript or any other language feature.

Scratch is an introductory language. Some people who use Scratch probably don't even know what a “print” is. So, if they check their coding in another language like JavaScript or Lua, they'll probably not even know what it means, and this is just MY theory, but Scratchers might question why it's broken, even though it's literally not. (take this with a grain of salt)

Like you said, how will the Scratcher know? They will need to get taught or follow tutorials. It’s not any different from moving to another language. CodeKingdoms (I’m not sure if I’m allowed to say that name) has a feature called “Epic Mode” and it constantly bugs. I don’t see why scratch would be any better.

7e_x

cookedasparagus8 wrote:
There are many flaws in your argument. Let’s break them down.
7e_x wrote:
Number 2, ONLY make it available for Scratchers.

Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text

So you think once you reach Scratcher status, you have outgrown scratch? There is a reason why the user keeps using Scratch and hasn’t moved on to harder programming languages.

true, but it would use the same block naming layout as scratch does, so

when green flag clicked

would become when green flag clicked

cookedasparagus8

7e_x wrote:
cookedasparagus8 wrote:
There are many flaws in your argument. Let’s break them down.
7e_x wrote:
#snipped
So you think once you reach Scratcher status, you have outgrown scratch? There is a reason why the user keeps using Scratch and hasn’t moved on to harder programming languages.
true, but it would use the same block naming layout as scratch does, so
when green flag clicked
would become when green flag clicked

This would still not be implemented because how are you going to convert “when green flag clicked” into “public static void main(String args())”?

Last edited by cookedasparagus8 (Jan. 2, 2026 13:52:44)

jmdzti_0-0

OP wrote:
Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text coding.

I already had some experience as a New Scratcher on my first account because I was already using the offline editor.

Restricted cloud variables are to prevent abuse, not because “only more experienced users will understand them.” I don’t think Scratch will purposefully gatekeep a feature that literally cannot be abused. (same with download to javascript, although it is already rejected for completely different reasons)

Last edited by jmdzti_0-0 (Jan. 2, 2026 14:08:06)

Object_3

Wait. The suggestion is to have the ability to see code like this:

When green flag clicked
Move x steps

Instead of

when green flag clicked
move () steps

Just making sure if that’s what you mean because I honestly can not understand

Last edited by Object_3 (Jan. 2, 2026 15:48:17)

CodeComet6161

…
This extends to coding, viewing, converting, or downloading Scratch in any text-based language, including BBCode, Javascript, some form of pseudocode, or some other programming language.

wallaceji

Support. How would knowing what code looks like behind the blocks not be beneficial? The ST is trying to limit our understanding of programming, which is already not beneficial.

7salad3salad

wallaceji wrote:
Support. How would knowing what code looks like behind the blocks not be beneficial? The ST is trying to limit our understanding of programming, which is already not beneficial.

This would not show the code behind the blocks. It would only show the blocks themselves as text code.

Kanyata

7e_x wrote:
READ FULL OP BEFORE GIVING YOUR OPINION!
So, as you may have known, text-based Scratch coding has been rejected:
the official list of rejected suggestions wrote:
2.2 Text-based syntax in Scratch
Some users wish to code Scratch not with the blocks, but with typing code instead (similar to how more advanced programming languages work). Others are interested in an option to view, convert, or download Scratch code to other programming languages. However, the Scratch Team has discussed this possibility multiple times and has decided every time that it would not be beneficial for beginners or teachers.

This extends to coding, viewing, converting, or downloading Scratch in any text-based language, including BBCode, Javascript, some form of pseudocode, or some other programming language. If you wish to code using another language, then you can learn it on your own, but it would have to be done outside of Scratch.
Well I have an idea, which could make text-based coding WORK.

So, number 1, DO NOT make it the default option.

Scratch is supposed to be an easy programming language. The main audience is 8-16 year olds, and a kid would get confused if they just saw a weird coding space where you type random stuff. Make it a separate option. Call it “Text Code” and make it a setting. (thank you 7salad3salad)

Number 2, ONLY make it available for Scratchers.

(Some) Scratchers have more experience on Scratch. Ya know how Scratchers can only use cloud variables? Do the same thing with text coding, as New Scratchers would probably check random menus to see what they do, and they would probably get stuck on text coding.

Number 3, do NOT make a download to JavaScript or any other language feature.

Scratch is an introductory language. Some people who use Scratch probably don't even know what a “print” is. So, if they check their coding in another language like JavaScript or Lua, they'll probably not even know what it means, and this is just MY theory, but Scratchers might question why it's broken, even though it's literally not. (take this with a grain of salt)

Number 4, use the same naming for the pieces of code as Scratch does.

It takes time to use a text-based programming language, so you can't add another language to Scratch. Use the same names as the blocks does in regular Scratch, so a piece of code looks like this:

when green flag clicked
move (10) steps
say [Meow!] for (2) seconds

This way a Scratcher could get into text coding right away.

So, yeah, that's it for now. Hope the Scratch Team reconsiders this suggestion and might add it in a different way. The end.

No support, someone who only knows how to code with blocks, or Is a new scratcher, could remix a text project, but not be able to add to it, basically making it impossible to remix, destroying remix culture.

Bitebite12

How would this be beneficial? Other than improving typing, I don't see benefits like learning general syntax structures and commands.

IloveRoblox003

wallaceji wrote:
Support. How would knowing what code looks like behind the blocks not be beneficial? The ST is trying to limit our understanding of programming, which is already not beneficial.

You may or may not be in the wrong suggestion
Or be misunderstanding it

But anyways
The inspect element exists, for your.. reasons

You are exaggerating ST’s lack of action. Must you blame the space industry for not creating a lot of successful rockets?

Anyways, no support. I would post something about mobile support, but I’ll move to a different reason.
There are things that we have to consider:
What is the error handling for a mistyped block?
And will the partly depreciated rule 4.4 of TOU apply to mistyped blocks?

Assuming 2 is true, it would go against 4.4. Assuming mistyped blocks are deleted, that would just delete a bit of hard work. Same with converting them to custom blocks.

Last edited by IloveRoblox003 (Jan. 8, 2026 03:44:31)

ilIusionator

Bitebite12 wrote:
How would this be beneficial? Other than improving typing, I don't see benefits like learning general syntax structures and commands.

ok so I'm pretty sure that the OP is suggesting an option to see scratch code as text but not an actual coding language
so now I form opinion!

I see no reason for this to be added. I feel like you made this suggestion just so you figured out a way “around” the rejection.

the whole reason why we want an option to change scratch to JavaScript or something is so we can learn it faster. There's no point in doing scratch block to scratch text because there's nothing to learn besides boolean means <> and operator means ( ), which is pretty meaningless.

ANALOGY TIME!!
You speak English, but you're wanting to learn French (Like knowing scratch but wanting to learn JavaScript)
Here's what you do:
You look at both an English sentence on your computer and then you translate it to a French one, you can point out similarities and get a good sense of the language. (Exactly what you would happen if you translated scratch to JavaScript)

Now,
if you do the same thing but translate a German sentence to Austrian German (a variation of German that's pretty similar to standard German with a few exceptions), you aren't going to learn much and it would just be a waste of time. (exactly what would happen if you translated scratch code blocks to scratch code text)

It's the same with code blocks to text code. It's a waste of time.

Last edited by ilIusionator (Jan. 8, 2026 03:44:22)

Discuss Scratch