When you write code for a “runtime” that wasn’t intended to run your code.

That definition would be too broad, as includes any type of exploit.

In ROP, you modify the stack to write return addresses and then return to jump to the first of these addresses, the return addresses go to parts of the executable that end with a return instruction (gadgets), so it will always return to the next of your return address.

(That video is maybe not the easiest introduction to ROP.)

Having ROP in here as normal programming paradigm, as opposed to vibe coding, made the meme so much better.

Relevant xkcd: https://xkcd.com/2597/

Either that or incest porn.

Then we’ll ship you and your sister.

Might depend on your file browser.

You may also want to try, for example, the files “a1”, “a2”, “a3”, and “a10”. Lexicographically, “a2”>“a10”, but my file browser displays “a10” after “a2”.

Think the other way around: What’s the use case for case insensitive file names? Does it justify the effort and complexity for the filesystem and the programs to know the difference between lower and upper space chars?

Regular expressions in general, and automata theory, sure you should know about that. But a specific extended regex language like here? That’s like saying you’re shit at coding if you can’t do <insert arbitrary programming language here>.