Pythonic Whitespace

Why does /prog/ dislike Python's use of whitespace? I have never had any problems with Python concerning whitespace, but numerous with C/C++.

Problems with C-style whitespace/bracing:
1) Code can be misleading, because while one reads indentation, it's not significant to the grammar. For instance:

if(true)
    a();
    b(); // This isn't actually in the body of the if.
2) There are over 9000 different ways of aligning bracing. Somehow, the most popular involves wasting a whole line for the opening brace'{'. Interestingly, such code always seems to neglect blank lines everywhere, leading to abominations like:

int a, b;
char c;
if(true)
{
    // do something
}
Why is the line of the if grouped together with the declarations of the variables!? What is wrong with the more readable and structured?:

int a, b;
char c;

if(true) {
    // do something
}
One can't say it's because the blank is a waste, because they often use nearly blank lines with solely '{' all the time!

Of course, Python saves even another line by eliminating the need for a closing brace '{'.

tldr: Why is Python's use of whitespace bad?

>>38
You know, there's programs/mini-programs/routines that could indent such code for you. If you editor doesn't have them, it sucks.

Also, you shouldn't even have that freedom/option, because eventually at some point in time, somebody else is going to have to read your code, and they're going to hate you for it. If you let people abuse something, they will. And so for indenting/bracketing, I think the option to abuse it should be abolished all together, for the good of the public.

>>40
Don't use ad-hominem attacks please.