In f#'s case, there is the trifecta of everything being an expression, static typing and default immutability. This means you often write code like this:

let foo = if bar then baz else someDefault

Due to it being an expression you assign what the if evaluates to to foo. Due to static typing, the compiler checks that both branches return the same type. Due to the default immutability you don't declare and assign in separate steps. What this results in, is that accidentally using the wrong indentation for something usually results in an error at compile time, at the latest.

Compared to how python does significant whitespace is that it's dynamic typing + statement based, which means you can easily end up assigning different types to the same variable in different branches of an if, for example.

I hope I explained it in understandable terms

> How so?

Well I don’t know what issue you have with whitespace, but the usual complaint is that programs with small typos are syntactically valid but logically incorrect. This is why CoffeeScript became so disliked. A static type checker makes this scenario much less likely since it won’t compile.

I would also add that F# has some indentation rules (“offside rules”) and tabs are disallowed, further shrinking the input space.