The unary `not` operator must be one of the worst crimes ever committed in language design. Who thought it was a good idea to add an almost invisible operator that *completely flips* the behaviour often leading to the opposite of the expected control flow from a glimpse.

I suspect this stems from an even deeper issue from languages of the C family. They've locked themselves to a rather inefficient and bad grouping/calling syntax which is so ugly to the point where simple operations like `not` had to be turned into syntactic sugar instead just so they could avoid having to use the mess they themselves created.