WolfCat67 wrote:

Hmm. Seems that “workaround-able” wasn't really taken into consideration too much when a new block was added into Scratch 3.0:

glide (1) seconds to [mouse-pointer v] :: motion

Clearly, this block can easily be worked around, but it looks like it was implemented regardless.

I don't know what I think about the above example, but I still think “it's workaround-able” is a valid reason to no support a suggestion.

However, this clearly shows that it doesn't matter whether or not it's easily workaround-able, but rather the usefulness as a block and whether or not it takes away from the educational aspect of the site.

I have the workabout:

glide (1) secs to x: ([x position v] of [Target Sprite v]) y: ([y position v] of [Target Sprite v])

Although the ST probably did not see this.

Support, unless the workaround is extremely easy.

Some people say that an exponent block isn't needed, because of the workaround. Well, the workaround involves at least 5 blocks, including involving logarithms and the constant e. A lot of new Scratchers don't even know what “e” is!

No Support, There's A Workaround

I'm joking. Semi-Support? This really isn't a suggestion.