-iviedwall- wrote:

Za-Chary wrote:

But then whenever I want to use a basic forever loop, instead of simply writing

I'd have to put a “not” block inside this:

That's overall more blocks. Now, the natural follow-up question is “Why wouldn't you just use a forever loop?” Well… what if I eventually decide that I need to put a boolean in my loop? Then I'd have to replace all the loops which will be more work. I'm looking for less work and less blocks here.

On another note, is it possible that “repeat until” is more intuitive than “while” for beginners?

So you're not gonna implement this just because you need another block? C'mon, that sounds lazy. If that's ST's logic, why don't you actually make infinity blocks used for smooth gliding, jumping, animating, and different functions that can just be done with a few blocks?

That isn’t his logic exactly. Normally, I will admit that isn’t a very good excuse, but this is talking about replacing a block, not adding one. I’d say the rules are a little bit different in this case, as more people will want to pull off a repeat until (at least that will be likely) but the while block makes them add another. Basically, which is more convenient to make the same function.

Support!
I have actually tried to suggest this myself. Yes, it is more typical and would do better about teaching people how to code.