Okay, so I've been seen a lot of trouble with the < [] = [] > block, specially on complex projects like base64 encoders & decoders, SHA256, and so on. That's why I'm introducing a new idea:

—————————————————————————————————————————————————————
The < [] ≡ [] > block.

<[] ≡ []::operators>//The block visualized

1. Starting up
   «≡» means identical to in maths, but also in text.
   
   
2. Okay, how would this work?
   Unlike the < [] = [] > block, this block would compare the Unicode characters of both strings, so it would be case sensitive. Let's see some comparsions here
   
   
3. Sure! But I'm pretty sure that there's a workaround for it
   
   The workaround (and doesn’t support all characters):
   
   credit to @FancyFoxy

YES.
While I can’t think of a situation when this would be necessary on the spot, there’s definitely some situation.
Other case sensitive blocks have been suggested (not dupes, different type of blocks) but this is by far the best one imo, support.

bump

Duplicate of https://scratch.mit.edu/discuss/topic/357768

TheCOUT-Test wrote:

Duplicate of https://scratch.mit.edu/discuss/topic/357768

Not exactly — that suggestion is about making an option, this one is about making a whole new block.

jmdzti_0-0 wrote:

TheCOUT-Test wrote:

Duplicate of https://scratch.mit.edu/discuss/topic/357768

Not exactly — that suggestion is about making an option, this one is about making a whole new block.

That suggestion would apply to every block though, including this one