Scratch

Greenatic wrote:

EdnaC wrote:

In any case, this block isn't going away - You could work around not having it (but suffer a small performance hit), but this is true of a lot of blocks.

Consider the following two obsolete blocks:

rewind sound
say nothing

These were removed because they could easily be done with other blocks, were glitchy, or weren't necessary.  For example, although I haven't used the rewind sound before, I believe it works like this:

stop all sounds
play sound

And say nothing could be done by ending the script.

So--the Scratch Team believed that since both of these blocks could be easily accomplished with other blocks, they should be removed.

So why is it even vaguely necessary to use forever if?  Because of a slight increase in speed?  Is that worth confusing many new Scratchers, and clogging up the block palette?

I don't think so.

rewind sound actually played the sound backwards, even more useless

1. There is nothing wrong with it.
2. It is a convenience.
3. People are used to using it.
4. People are used to knowing it's there.
5. It can be make things easier for new scratchers.
6. It is implemented in older projects already.
7. Deleting it would cause complaints, not praise.
8. Unnecessary work for the Scratch team.

scimonster wrote:

acedannyk wrote:

1. There is nothing wrong with it.
2. It is a convenience.
3. People are used to using it.
4. People are used to knowing it's there.
5. It can be make things easier for new scratchers.
6. It is implemented in older projects already.
7. Deleting it would cause complaints, not praise.
8. Unnecessary work for the Scratch team.

1) It confuses people.
2) Maybe... 1 millisecond faster running, 10 seconds faster programming.
3) And people are not used to making custom blocks, but they'll get used to it.
4) People aren't used to the new blocks in 2.0; people can change what they're used to.
5) It can also make it harder.
6) Which is why it would still run, it just wouldn't be in new ones.
7) No complaints from the supporters!
8)    They're already redoing all of Scratch, is moving one little block gonna hurt them so much?

*cracks knuckles*
1. Does everyone understand the trigonometry blocks etc? Everyone will learn eventually.
2. That's good right?
3. If they are used to it, why take it away? It is handy.
4. If they are used to it, why take it away? It is handy.
5. Help options are always there for EVERY block.
6. It may cause some confusion to Scratchers who haven't seen it before.
7. Who will seriously be saying 'thanks for taking away a perfectly working block!'
8. No.
9. Nobody is forcing anyone to use the block.
10. Users have a choice of speed or flexibility, Why take away an option?

I agree — there's no difference between "forever if (...)" and "forever( "if (...)" )"

Leo_the_Lion wrote:

There's nothing WRONG with the block. If you don't like it, don't use it. I don't see how deleting it would help, considering some people use it very much. Whether or not it would interfere with player or download, Forever If is a useful block for beginners and advanced users. Deleting it wouldn't have a particular purpose. If you don't want the block clogging up space or want to use more than one IF, just don't use the block? Why delete it?

Agree 100%

BoltBait wrote:

bobbysq wrote:

It also sounds like it does the same as

<wait until>
<forever>

That's not how it works, but many people believe that it is.

That was my point. I was younger at the time, so the wording was sort of bad.

I Partly Support

BURN THE

 forever if <  > 

everybodyedits wrote:

BURN THE

 forever if <  > 

BLOCK!

Don't necropost

That doesn't require a necropost