Discourage "easy workaround" no-supports

ajskateboarder

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

Elaborate, please? This doesn't make sense

Last edited by ajskateboarder (Oct. 30, 2023 16:24:32)

MagicCoder330

KingRat_1 wrote:
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

This is a valid point, and is true in some respects. Perhaps there should be some sort of dropdown from the main categories, such as operators having a “Math” category.

amogus1123

MagicCoder330 wrote:
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.

a lot of workarounds are pretty easy to understand loool.
scratch has more important things to do being unprofited.
And note that lots of blocks won't always cause lag, it also depends on audio and sprites.

Last edited by amogus1123 (Oct. 30, 2023 17:22:57)

Elijah999999

Depends on how “easy” these workarounds are.
Previous costume? Easy.

((costume #) - (1))

If on edge bounce? Not as easy. I can't even think of a workaround for it.
Move () steps? Easy if you know how sin and cos work. But it still is a bit advanced for younger Scratchers, so it's still a handy block.

amogus1123

Elijah999999 wrote:
Depends on how “easy” these workarounds are.
Previous costume? Easy.
((costume #) - (1))
If on edge bounce? Not as easy. I can't even think of a workaround for it.
Move () steps? Easy if you know how sin and cos work. But it still is a bit advanced for younger Scratchers, so it's still a handy block.

if on edge bounce yee…

deck26 posted this on helpwithscripts just now
https://scratch.mit.edu/projects/99412537

waitwhat2288

The Scratch Team shouldn't be the one that goes out of their way to discourage others from using these kinds of counterarguments if we as a whole can do essentially the same thing.

Nonetheless, we've been the ones to discourage others from creating workarounds for another person's proposed block, so why do we need to discourage it even more?

MagicCoder330

when green flag clicked
if <[page number] > [1]> then
broadcast [Bump v]
end

medians

Elijah999999 wrote:
Depends on how “easy” these workarounds are.
Previous costume? Easy.
((costume #) - (1))
If on edge bounce? Not as easy. I can't even think of a workaround for it.
Move () steps? Easy if you know how sin and cos work. But it still is a bit advanced for younger Scratchers, so it's still a handy block.

Then again, these exist:

amogus1123

medians wrote:
Elijah999999 wrote:
Depends on how “easy” these workarounds are.
Previous costume? Easy.
((costume #) - (1))
If on edge bounce? Not as easy. I can't even think of a workaround for it.
Move () steps? Easy if you know how sin and cos work. But it still is a bit advanced for younger Scratchers, so it's still a handy block.
Then again, these exist:

???
Those are for the previous backdrop, not previous costume

YtArie5

Aren't these already discouraged?

medians

amogus1123 wrote:
medians wrote:
Elijah999999 wrote:
Depends on how “easy” these workarounds are.
Previous costume? Easy.
((costume #) - (1))
Then again, these exist:
???
Those are for the previous backdrop, not previous costume

Why have the next/previous/random backdrop, and next costume blocks but no previous/random costume block.. did you read the these exist part lol

Last edited by medians (Oct. 31, 2023 21:43:08)

amogus1123

people saying
“No support, there is a workaround:”
(⌐⊙_⊙) (⌐⊙_⊙)

Mogus_man

no support, workaround

MagicCoder330

minecraftmanpp_tutor wrote:
no support there is a workaround /j

Mogus_man wrote:
no support, workaround

Peneren wrote:
No support, there is a workaround

ow my head

BasisEssence779

Most issues happen with some workarounds because they lower the performances, resulting to poor FPS especially in mobile devices that are less powerful than the PC I use.

I will give examples tomorrow because I most go to sleep now.

doggy_boi1

yadayadayadagoodbye wrote:
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

no support for this reason ^

gdfsgdfsgdfg

Some blocks with easy workarounds like

forever if <> {

} :: cap control loop

are removed not cuz of the workaround
but cuz of confusion
so there is no reason to discourage this

MagicCoder330 wrote:
ow my head

I thought they were mocking your suggestion?

Last edited by gdfsgdfsgdfg (Oct. 31, 2023 22:29:27)

medians

gdfsgdfsgdfg wrote:
Some blocks with easy workarounds like
forever if <> {

} :: cap control loop
are removed not cuz of the workaround
but cuz of confusion
so there is no reason to discourage this

That's not what they're saying, they mean stuff like this:

original poster wrote:
I think that there should be a block reporting the current rotation style of a sprite:
(rotation style ::motion)

replier wrote:

No support, easy workaround:

define set rotation style to (string1)
set [rotation style v] to (string1)
set rotation style (string1)

Or:

original poster wrote:
I think that there should be a previous costume block because there is a next/previous backdrop block as well as a next costume block.
switch costume to [previous costume v]
or
previous costume ::looks

replier wrote:
No support, easy workaround:
define previous costume
switch costume to ((costume #) - (1))

Though these are already discouraged, so..

Last edited by medians (Oct. 31, 2023 22:34:10)

undeterminstic

MagicCoder330 wrote:
minecraftmanpp_tutor wrote:
no support there is a workaround /j
Mogus_man wrote:
no support, workaround
Peneren wrote:
No support, there is a workaround

ow my head

i used /j because it was a joke

gdfsgdfsgdfg

medians wrote:
That's not what they're saying, they mean stuff like this:

I think I misread it again but
some quote and quote “easy workaround” blocks
aren’t here only because of a simple workaround
it’s about the understanding and other stuff

Last edited by gdfsgdfsgdfg (Oct. 31, 2023 22:45:27)

Discuss Scratch