A lot of great suggestions are no supported because there is a workaround. However, new scratchers have trouble with some workarounds a lot of the time, and I'm sure more advanced scratchers would appreciate if some things were simpler. I'm not saying they should be banned, but they should be discouraged. It would also make it so more suggestions are taken seriously. On top of that, workarounds often contain several blocks which can make the coding space cluttered quickly, while making it confusing to remix for newer scratchers. It can also make lower end devices lag, which many people do not enjoy.

In a nutshell, “easy workaround” no-supports should be discouraged because workarounds are confusing to new players, and they can clutter the workspace quickly while making it more laggy for lower end devices, while single blocks would be faster and easier for more advanced scratchers to use.

Some workarounds are not hard for New Scratchers to understand. Just because they're new doesn't mean they're dumb.

sonic__fan wrote:

Some workarounds are not hard for New Scratchers to understand. Just because they're new doesn't mean they're dumb.

Yes, I am aware of this, but I remember when I was new I had trouble with workarounds.

MagicCoder330 wrote:

sonic__fan wrote:

Some workarounds are not hard for New Scratchers to understand. Just because they're new doesn't mean they're dumb.

Yes, I am aware of this, but I remember when I was new I had trouble with workarounds.

Just because you had trouble with workarounds doesn't mean other people will.

sonic__fan wrote:

MagicCoder330 wrote:

sonic__fan wrote:

Some workarounds are not hard for New Scratchers to understand. Just because they're new doesn't mean they're dumb.

Yes, I am aware of this, but I remember when I was new I had trouble with workarounds.

Just because you had trouble with workarounds doesn't mean other people will.

I know, I just think that it would be easier for people if it were made more simple. And besides, this is starting to deviate from the original topic.

It heavily depends.

Block suggestions work on a “difficulty” to “frequency” to “usefulness” ratio

If something is very difficult, isn’t used a lot, and wouldn’t be very useful, it’s better than something that isn’t any

If something is easy, but used very often, and would be somewhat useful, then it’s okay

no support there is a workaround /j

cookieclickerer33 wrote:

It heavily depends.

Block suggestions work on a “difficulty” to “frequency” to “usefulness” ratio

A removed block which passes all the requirements is this bad boy

all at once

end

A insanely useful block that meets all the requirements above, easy to understand, useful for many purposes, and will be used a decent bit. that is a example that sometimes the workaround is more trouble than its worth.

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

pretty sure those are already unconstructive though

epicdude512 wrote:

(#8)
-snip-

actually in scratchblocks to do a c block you need to do a opening-curly bracket (aka {) and then newline and then closing-curly bracket (aka }).

all at once{
} :: control

EDIT: i can grammar

sonic__fan wrote:

Some workarounds are not hard for New Scratchers to understand. Just because they're new doesn't mean they're dumb.

^^

Even complex workarounds can be grounds for suggestions to be rejected, simply because the Scratch Team cares a lot more about making Scratch easy to learn and make simple games with than making advanced techniques easier. (I disagree with the ST on this point, but it is what it is.)

1. It is already discouraged
2. “workaround” no supports sometimes makes sense, as things could be too specific to add a block for, or it could be that it'd be essential for people to learn how to do something rather then being provided a function for it

epicdude512 wrote:

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

it isn't that hard i use it all the time millions of scratchers do

minecraftmanpp_tutor wrote:

epicdude512 wrote:

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

it isn't that hard i use it all the time millions of scratchers do

I agree, and maybe a little note could be made underneath that says if you check this box then it will make all code run as fast as possible, and will try to finish the code before update the screen or canvas.

IndexErrorException wrote:

minecraftmanpp_tutor wrote:

epicdude512 wrote:

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

it isn't that hard i use it all the time millions of scratchers do

I agree, and maybe a little note could be made underneath that says if you check this box then it will make all code run as fast as possible, and will try to finish the code before update the screen or canvas.

Discuss somewhere else, this is about workarounds not screen refresh

BobRocks20 wrote:

IndexErrorException wrote:

minecraftmanpp_tutor wrote:

epicdude512 wrote:

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

it isn't that hard i use it all the time millions of scratchers do

I agree, and maybe a little note could be made underneath that says if you check this box then it will make all code run as fast as possible, and will try to finish the code before update the screen or canvas.

Discuss somewhere else, this is about workarounds not screen refresh

Excuse me, it's pretty close to workarounds.

The issue stems from people will have a one-time rare need for something they either don't know to make in Scratch and then make a suggestion.

IndexErrorException wrote:

BobRocks20 wrote:

IndexErrorException wrote:

minecraftmanpp_tutor wrote:

epicdude512 wrote:

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

it isn't that hard i use it all the time millions of scratchers do

I agree, and maybe a little note could be made underneath that says if you check this box then it will make all code run as fast as possible, and will try to finish the code before update the screen or canvas.

Discuss somewhere else, this is about workarounds not screen refresh

Excuse me, it's pretty close to workarounds.

The issue stems from people will have a one-time rare need for something they either don't know to make in Scratch and then make a suggestion.

Wait, what does screen refresh have to do with discouraging not supporting because of a workaround? I would like epicdude512 to elaborate on this in connection to the suggestion:

epicdude512 wrote:

The, replacement run without screen refresh is really hard for anyone to understand, never used, and is practically useless due to how much work you have to do

P.S. I'm not feeling well because of congestion so that's why I'm confused

this is a bumb or something

MagicCoder330 wrote:

which can make the coding space cluttered quickly

I would argue that a bunch of unnecessary blocks would clutter the coding space more

No support, there is a workaround:
Don't read them.

Peneren wrote:

(#19)
No support, there is a workaround:
Don't read them.

Aaaaaaaand have them not contribute to the discussion by posting something unconstructive.

Yeah, that sounds about right, definetly helps the discussion.